This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc_tooldir is useless
- To: "Rask Ingemann Lambertsen" <rask at kampsax dot k-net dot dk>
- Subject: Re: gcc_tooldir is useless
- From: Andreas Schwab <schwab at suse dot de>
- Date: 21 Sep 1999 19:12:21 +0200
- Cc: "GCC mailing list" <gcc at gcc dot gnu dot org>
- References: <1012.932T271T11673671@kampsax.k-net.dk>
"Rask Ingemann Lambertsen" <rask@kampsax.k-net.dk> writes:
|> Den 20-Sep-99 08:32:29 skrev Andreas Schwab følgende om "Re: gcc_tooldir is useless":
|>
|> > When the libstdc++ library is compiled the compiler won't find the system
|> > headers in $(tooldir)/include, since $(gcc_tooldir) does not exist.
|> > I wonder what's wrong with using $(tooldir) in the first place? If, say,
|> > $(libdir) is a symlink to some unrelated directory then this will never
|> > work, even after installation.
|>
|> I've seen such problems trying to build a cross compiler, I think. What
|> _is_ the difference between $(tooldir) and $(gcc_tooldir)?
$(gcc_tooldir) is logically the same as $(tooldir), but contains some ".."
parts that are supposed to lead relatively from $(libsubdir) to
$(exec_prefix). This will fail if any component between $(prefix) and
$(libsubdir) does not exist or is a symlink to some unrelated directory.
Andreas.
--
Andreas Schwab "And now for something
schwab@suse.de completely different."
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg