This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc_tooldir is useless
- To: Andreas Schwab <schwab at suse dot de>
- Subject: Re: gcc_tooldir is useless
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Tue, 28 Sep 1999 02:14:41 -0600
- cc: "GCC mailing list" <gcc at gcc dot gnu dot org>
- Reply-To: law at cygnus dot com
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).
The exception is when we do crosses for VxWorks, in which case the includes
get copied via the --with-headers support code in configure, which are
copied into $tooldir/sys-include.
jeff