latest snapshot won't find C++ header files

Richard Earnshaw rearnsha@arm.com
Mon Oct 12 06:30:00 GMT 1998


manfred@s-direktnet.de said:
>  2. The second problem arises from the fact, that, provided you're
> building
>     a *new* snapshot, $(libsubdir) usually *does not already* exist!
> If
>     now $(libsubdir)/$(unlibsubdir) with unlibsubdir=../../.. is used
> to
>     locate "as", "ld", "include" (did I miss anything?), the just
> built
>     "xgcc" will simply fail and revert to its "second" default, e.g.
> using
>     "/usr/ccs/bin/as" on HP-UX or Solaris.  Creating an empty
> $(libsubdir)
>     before "make bootstrap" would cure this, but simply adding
>     "-B${exec_prefix}/${target}/bin" to the appropriate ..._CFLAGS
> might
>     be the better solution (again, this is, what Alexandre suggested
> in his
>     email). 

It might solve the binaries problem, but I can't see how this would solve 
the includes problem.  Also, I wasn't aware that -B options were additive 
(ie you could have more than one): if this is the case (that they aren't) 
then the -B must be set to the current build directory during the compile 
process, so that xgcc can find the correct cc1.

Another solution might be to have code to translate .../foo/../b into 
.../b if the initial lookup fails -- this code might also be problematic 
because it won't respect symlinks.

Richard.




More information about the Gcc-bugs mailing list