This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Makefile.in FLAGS_TO_PASS: why pass *_FOR_TARGET variables?
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: Makefile.in FLAGS_TO_PASS: why pass *_FOR_TARGET variables?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 02 Aug 1998 01:30:55 -0600
- cc: egcs at cygnus dot com
- Reply-To: law at cygnus dot com
In message <9808020718.AA34052@marc.watson.ibm.com>you write:
> I am not refering to the top-level Makefile -- I am sorry that I
> did not make that more clear. All of my comments were in reference to
> gcc/Makefile.in .
Ah. In that case, the gcc/Makefile code to pass the _FOR_TARGET stuff
around may be historical, or due to copying code from the toplevel
Makefile.in without eliminating stuff that isn't needed.
I suspect we could probably just stop passing the _FOR_TARGET things
around to the language subdirs, except {GCC,OBJC,CXX}_FOR_TARGET.
One day it should be possible to avoid passing any FOR_TARGET crud
around in the gcc dir since we want to move runtime stuff out of
the language subdirs (and it's building the runtime stuff that needs
all the FOR_TARGET crap).
jeff