This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: libstdc++, autoconf, and /lib/cpp (was Fw: Re: GCC 3.0 Status , Report)


On Wed, May 02, 2001 at 04:08:40PM -0700, Benjamin Kosnik wrote:
> > #   --with-headers=dir -- Specifies a directory which has target include
> > #   files. This options is required when building a cross compiler, if
> > #   ${prefix}/${target}/sys-include doesn't pre-exist.
> 
> shouldn't have to do this

Shouldn't have to do either one, or shouldn't have to do the --with?


> > Wouldn't that be tricker than calling just the preprocessor?  If the system
> > headers aren't being found during configure, then things are only going
> > to get worse.
> 
> The thought is that CXX gets passed down and set correctly, whereas CPP 
> isn't or doesn't, I'm not quite sure which. So, it might be an effective 
> work-around to just use AC_TRY_COMPILE, and thus CXX. 

CXXCPP is being passed down, it's just incorrect because autoconf believes
that "xgcc -E" doesn't work properly (since stdlib.h couldn't be found).

It feels like we're papering over a problem... i.e., if things like
stdlib.h can't be found by the newly-built xgcc during configure, I can't
wait until we actually try and compile the library.


Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]