This is the mail archive of the
mailing list for the GCC project.
Re: Is it ever possible to build libmudflap, libssp, or libgomp when inhibit_libc is set?
- From: Ian Lance Taylor <iant at google dot com>
- To: skenton at ou dot edu
- Cc: gcc at gcc dot gnu dot org
- Date: 08 Oct 2007 08:00:11 -0700
- Subject: Re: Is it ever possible to build libmudflap, libssp, or libgomp when inhibit_libc is set?
- References: <47070EF6.email@example.com>
Steve Kenton <firstname.lastname@example.org> writes:
> Is it ever possible to build libmudflap, libssp, or libgomp when
> inhibit_libc is set?
It seems unlikely.
> If not, is is reasonable to add a check to the top level configure to detect
> situations that will cause gcc configure to set inhibit_libc and add those
> libraries to either skipdirs or noconfigdirs. (Which would be preferred?)
> It looks like just a couple of lines in configure to exclude them
> if they can never build under that condition on any target.
That seems reasonable in principle. They should be added to
skipdirs. Ideally the condition expressing when inhibit_libc should
be set should be done in a single place, and then somehow communicated
to other places.
In the current inhibit_libc condition I don't understand the
interaction between --with-newlib and --with-headers. If newlib is
available, inhibit_libc normally should not be defined.