Re: gcc_tooldir is useless

[Andreas Schwab <schwab at suse dot de>]

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

|>   In message <jepuzb815x.fsf@hawking.suse.de>you write:
|>   > Jeffrey A Law <law@cygnus.com> writes:
|>   > 
|>   > |>   In message <jeyadz82fo.fsf@hawking.suse.de>you write:
|>   > |>   > Do you build the C++ compiler?  While builing the libstdc++ library 
|>   > the
|>   > |>   > target headers will not be found, since $(gcc_tooldir) does not exis
|>   > t,
|>   > |>   > until you install the current compiler version the first time.
|>   > |> Most definitely.  And the C++ runtime libraries.
|>   > 
|>   > Do you have the target includes in $(tooldir)/include?
|>   > $(gcc_tooldir)/include won't find them if $(libsubdir) does not exist yet.
|> When we do our builds the target include files are usually in the source
|> directory (ie, we have a C library that is a sibling of the gcc directory).

Which is the reason why it works for you.  But I have already send a patch
to gcc-patches that fixes the case when the headers are in
$tooldir/include.  You just have to make sure that the target libraries
use the same compiler command as in the gcc directory when running the
target compiler.

Andreas.

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