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: Peter O'Gorman <peter at pogma dot com>
- To: Libtool Bugs <bug-libtool at gnu dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 01 Sep 2005 14:09:35 +0900
- 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>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter O'Gorman wrote:
| The problem is that libtool tries to run ranlib after install and that
| ranlib can fail if the library is not writable?
[crosspost - beware - for context see
<http://gcc.gnu.org/ml/gcc/2005-08/msg00937.html>]
When I look more closely at this, I see in libtool.m4:
old_postinstall_cmds='chmod 644 $oldlib'
and a little later:
old_postinstall_cmds="\$RANLIB \$oldlib~$old_postinstall_cmds"
Should that be:
old_postinstall_cmds="$old_postinstall_cmds~\$RANLIB \$oldlib"
??
Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)
iQCVAwUBQxaND7iDAg3OZTLPAQIenwQAw+FtzccBDNnixZdjK8gdI0Zaxu3xpX0D
9jPOkhPZaGMshTHF77W7h2ZxLmqmNwvWTlGjHCnwZXBuY3nW2Lms+ow0AZ9V+eP3
ADFRfvmlnkmkxl/pDiLKYPyCfJucuae1mAF8DMmWHN6gS3AknP0n4imybOp3GULd
FbSpIRKclJ0=
=COg3
-----END PGP SIGNATURE-----