latest snapshot won't find C++ header files
Jeffrey A Law
law@cygnus.com
Sat Oct 10 21:24:00 GMT 1998
In message < 13855.33419.398235.145221@saturn.hollstein.net >you write:
> > > The source of the problem is: the root directory for locating files is
> > > $(libsubdir), and this usually *does not exist while you're building a
> > > new snapshot*, hence assemblers, linkers, binutils, include files
> > > (forgot anything?) won't be found at build time.
> >
> > But they aren't currently found anyway, and they weren't found in the
> > install tree before. Moreover, I'm not trying to fix this problem,
> > I'm fixing *another* problem, so rejecting this patch because it does
> > not fix the binaries-not-found problem is unfair :-)
>
> I'm sorry, my intention was not to attack anybody or to reject your patch;
> if it sounded this way, I honestly apologize! I was only surprised (and
> perhaps somewhat angry) to see how many working things had been broken
> by this small $(unlibsubdir) patch :-)
Can someone please summarize the problems we need to address?
Again, it is my believe that changing configure.in to define unlibsubdir
to "." in those cases where it can not be made to work should fix both
problems.
But I may not understand the problems fully, so please explain
both problems we're having in detail.
> > In order to fix the binaries-not-found problem, wouldn't it be enough
> > to add another -B switch to GCC_FOR_TARGET, as well as to CC for
> > stages after stage1?
>
> I believe this would solve the problem, indeed.
No, that's not the right approach. If that's required, then the problem lies
elsewhere.
jeff
More information about the Gcc-bugs
mailing list