-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gerald Pfeifer wrote: |> |>Except that probably this has to get into libtool somehow or |>something. Hmmm. | | | Ouch, now you got me scared. I already started testing a patch to remove | the ranlib invocations that are part of the installation, but I'm afraid | that level of configury work described above execeed what I feel confident | hacking. | | Is anyone else going to give it a try, or should it just file a Bugzilla?
Hi, The problem is that libtool tries to run ranlib after install and that ranlib can fail if the library is not writable? Note that on darwin running ranlib on a 444 lib works and changes permissions to 644, remind me to file a bug. I would suggest continuing to run ranlib after install, but not failing if it does not work. You need to look for the variable old_postinstall_cmds in libtool.m4 and ltmain.m4sh (ltconfig and ltmain.sh in gcc??) and change either how it is set or how it is run. Another alternative would be to set RANLIB=: before configure if your system does not need to ranlib anything. Hope this helps, Peter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) iQCVAwUBQxZyhriDAg3OZTLPAQIpWgP9Fm5SHXP2X8CnpH7AAMkbSIcviisART3h r9D4sXo4xLB253Yw8hxPsO1I6lQBTSUGV6cpK9C6eZEzb20u5YlqILe8x1jM/DDN njjYOeY3Z9u7BQ0azKB8kE9FLzquDlpJ1hzJoBeKYYomFwilt5xXI+e74SPsskGf I2naJmvC+yA= =qEgR -----END PGP SIGNATURE-----
