Re: -mmacosx-version-min and libgcc

[Geoffrey Keating <geoffk at apple dot com>]

On 29/09/2005, at 4:21 PM, Ian Lance Taylor wrote:

> Geoffrey Keating <geoffk@apple.com> writes:
>
>
> > > Yes but I was not building in the top level but in the gcc sub-
> > > directory
> > > as I normally did when I wanted to start testing a patch or debug  
> > > GCC.
> >
> > Is this really supposed to work?  How?
> >
> > I always do 'make all-gcc' from the top level when I want to test a
> > patch or debug something new, because of problems like this one.
> > It's not just this variable, there are lots of others that are set
> > one way by the top-level makefile and not set or set differently by
> > the gcc makefile.
>
> For what it's worth, I almost always build in the gcc subdirectory,
> and it always works.
>
> For this particular case you just have to define STRIP_FOR_TARGET in
> the gcc Makefile.  It doesn't have to have precisely the same value as
> it does at top-level; it just has to work well enough for developers,
> not for users.

The problem with this is that there's no equivalent of  
TARGET_FLAGS_TO_PASS.  Exporting to sub-makes is done via environment  
variables, so if you explicitly set anything in the makefile that is  
the setting that wins in a sub-make (for instance, in a stage of a  
bootstrap).

> (But with today's infrastructure, if you want complete safety, have
> the top level configure script export STRIP_FOR_TARGET, have the gcc
> configure script pick up STRIP_FOR_TARGET from the environment and
> cache it (use the same value as top level if uncached) and then
> substitute STRIP_FOR_TARGET in gcc/Makefile.in.  Then for extra credit
> do the same for AR_FOR_TARGET and RANLIB_FOR_TARGET.)

Interestingly, as far as I can tell, there's no existing example of  
this in the GCC build system.  Are there really no other uses of  
*_FOR_TARGET that are supposed to be inherited from the top-level  
makefiles?

Attachment: smime.p7s
Description: S/MIME cryptographic signature