This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: look for host ranlib in configure
On Jan 3, 2001, Laurynas Biveinis <lauras@softhome.net> wrote:
> Alexandre Oliva wrote:
>> Hmm. I see EXTRA_HOST_FLAGS already passes RANLIB down; I hadn't
>> noticed EXTRA_GCC_FLAGS does too. And a number of rules pass the HOST
>> RANLIB down explicitly; these will be a tad bit harder to rewrite
>> portably.
> You mean, adding XFOO= in all places where [HOST-]RANLIB is passed down is
> not enough?
Unfortunately not.
> What else should be done.
There are two occurrences of:
"RANLIB=$${RANLIB}" \
within build rules, that will have to be adjusted similarly. I
had thought it would be trickier because I thought we were setting
environment variables, but it's just arguments to make, so the same
XFOO trick should work.
> Also, in my next patch I'm trying to move {RANLIB|NM|AR}_FOR_TARGET
> macros to configure too. Will it need similar treatment?
I believe so. In the top level, you should probably arrange for them
to be substed with $(AR), $(NM) and $(RANLIB) (as opposed to the
contents of $(AR), $(NM), etc) in case host_canonical =
target_canonical, and with the values they're regularly replaced with
otherwise. But this won't save us from duplicating the logic within
GCC's configure.in, since it should not depend on variables passed
from the top level. Or should it?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me