Re: gcc_tooldir is useless

[Andreas Schwab <schwab at suse dot de>]

Jeffrey A Law <law@cygnus.com> writes:

|>   In message <jehfkn9rk7.fsf@hawking.suse.de>you write:
|>   > I don't understand this.  $(prefix) is hardcoded, the relative distance
|>   > between $(libsubdir) and $(tooldir) is hardcoded, so where is the
|>   > advantage,
|> Once we know prefix, either via a -B argument or via argv[0] we can find
|> all the things we need.  header files, include files, libraries, etc etc
|> without using any hardcoded paths.
|> 
|>   > especially if building a cross compiler simply does not work?
|>   > Does the GCC team consider the case of building a cross compile as
|>   > unimportant?  That would be bad, IMHO.
|> That means something is broken.  I use this code *every day* to build cross
|> toolchains.

Do you build the C++ compiler?  While builing the libstdc++ library the
target headers will not be found, since $(gcc_tooldir) does not exist,
until you install the current compiler version the first time.

Andreas.

-- 
Andreas Schwab                                  "And now for something
schwab@suse.de                                   completely different."
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg