This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Running ranlib after installation - okay or not?

From: Shantonu Sen <ssen at opendarwin dot org>
To: gcc at gcc dot gnu dot org
Date: Thu, 1 Sep 2005 08:30:05 -0700
Subject: Re: Running ranlib after installation - okay or not?
References: <Pine.BSF.4.62.0508311718400.22973@pulcherrima.dbai.tuwien.ac.at> <m3wtm2kmsh.fsf@gossamer.airs.com> <0b7e9f70d997eb3033872da5db37f4c8@physics.uc.edu> <m3slwplxoq.fsf@gossamer.airs.com> <m3k6i1lxd2.fsf@gossamer.airs.com>

If you do change how this is implemented in the config* files, please make sure that you still support cross compiling to Darwin. In that case, the runtime libraries for the target would still run into this issue, because you'd be using the Darwin ranlib, even on a Linux build/host.

Shantonu

On Aug 31, 2005, at 12:28 PM, Ian Lance Taylor wrote:

Still, all this really means is that we should be host specific when
deciding whether or not to run ranlib.

In fact we are already host specific as to what flags we use.  On
Darwin we use -c, which we do not use on any other system.  Maybe we
should remove AC_PROG_RANLIB from configure.ac, and add something to
config.host instead.

Except that probably this has to get into libtool somehow or
something.  Hmmm.

Ian

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]