for glibc, "--disable-add-ons" generates a weird error

Robert P. J. Day rpjday@mindspring.com
Mon Dec 19 18:11:00 GMT 2005


On Mon, 19 Dec 2005, Josh Parsons wrote:

> Robert P. J. Day wrote:
> >   in testing my build script to see if it can build a non-thread
> > toolchain, i added the option "--disable-add-ons" to the glibc
> > configure step, which generated the amusing error:
> >
> > configure: error: add-on directory "no" does not exist
>
> >   is this what's *supposed* to happen?
>
> --disable-XXX is standardly equivalent to --enable-XXX=no in autoconf.
>
> The glibc manual suggests that --disable-add-ons is not supposed to
> be functional, quote: "If you do not wish to use some add-on package
> that you have present in your source tree, give this option a list
> of the add-ons that you /do/ want used".

well, the glibc *manual* might say that, but the actual
glibc/configure script says this:

# Check whether --enable-add-ons or --disable-add-ons was given.

  so this would be one of those times where RTFS'ing would not have
done you any favours. :-)

rday

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com



More information about the crossgcc mailing list