This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Running ranlib after installation - okay or not?
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Peter O'Gorman <peter at pogma dot com>
- Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, Ian Lance Taylor <ian at airs dot com>, gcc at gcc dot gnu dot org, Joe Buck <Joe dot Buck at synopsys dot COM>
- Date: Mon, 5 Sep 2005 12:53:31 +0200 (CEST)
- 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><Pine.BSF.4.62.0508312203410.22973@pulcherrima.dbai.tuwien.ac.at><43167287.4080907@pogma.com> <20050901201042.GC10948@synopsys.com><a1ac7d5f8b133b94d4b6d7c0f5f3b358@physics.uc.edu> <431790AC.4030500@pogma.com>
On Thu, 1 Sep 2005, Peter O'Gorman wrote:
> Another alternative would be to set RANLIB=: before configure if your
> system does not need to ranlib anything.
Thanks for the nice hint - this is what the FreeBSD Ports Collection
now uses for the lang/gcc34 to lang/gcc41 ports. ;-)
On Fri, 2 Sep 2005, Peter O'Gorman wrote:
> Doesn't matter, the solution I applied to GNU libtool cvs last night is
> probably most appropriate, i.e. chmod 644 before ranlib. I guess I'll look
> at gcc cvs over the weekend to figure out where that would go in your tree.
Cool, thanks!
Gerald