Re: -mmacosx-version-min and libgcc

[Ian Lance Taylor <ian at airs dot com>]

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.

(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.)

Ian