[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 1 of 2 v3] tools: check for documentation generation tools at configure time
On Fri, 2012-09-07 at 05:35 +0100, Matt Wilson wrote: > It is sometimes hard to discover all the optional tools that should be > on a system to build all available Xen documentation. By checking for > documentation generation tools at ./configure time and displaying a > warning, Xen packagers will more easily learn about new optional build > dependencies, like markdown, when they are introduced. > > Signed-off-by: Matt Wilson <msw@xxxxxxxxxx> While investigating an (unrelated) issue with the cronjob that generates http://xenbits.xen.org/docs/unstable/ I had a sudden though about a downside of this approach. Trying to run ./configure on xenbits results in: $ ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... no checking for cc... no checking for cl.exe... no configure: error: in `/home/xendocs/cronjobs/working/docs/unstable/tree/tools': configure: error: no acceptable C compiler found in $PATH See `config.log' for more details Which is a bit annoying if all you wanted was to build docs. I'm not sure I really want to advocate putting gcc on xenbits. I suppose I could put a dummy shell script in $PATH. AIUI autoconf allows you to define that a configure script calls a sub-configure script. Could we use this at the toplevel to call both tools/configure and a new docs/configure? Then my docs scripts could just call docs/configure? FWIW the unrelated issue was: $ make -C docs/ clean /bin/sh: gcc: not found /bin/sh: arithmetic expression: expecting primary: "" which I think is down to the gcc version check in Config.mk. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |