Hello! It's been some time, but still... On Mon, Dec 25, 2006 at 09:23:15PM -0800, Paul Eggert wrote: > Benoit Sigoure <tsuna@xxxxxxxxxxxxx> writes: > > > http://lists.gnu.org/archive/html/automake-patches/2006-10/msg00070.html > > I installed the following to Automake install-sh to implement > "install-sh -C", which is the second part of that patch. Thank you! I'm already using that one, it works fine. However now there is another issue, see this snippet: make[2]: Entering directory `[...]/libhurd-ihash.kernel.build' test -z "//lib" || /bin/mkdir -p "[...]/libhurd-ihash.kernel.build.install//lib" /bin/bash [...]/build-aux/install-sh -C -m 644 'libhurd-ihash.a' '[...]/libhurd-ihash.kernel.build.install//lib/libhurd-ihash.a' /bin/bash [...]/build-aux/install-sh -C -m 644 'libhurd-ihash-nomalloc.a' '[...]/libhurd-ihash.kernel.build.install//lib/libhurd-ihash-nomalloc.a' i686-pc-viengoos-gnu-ranlib '[...]/libhurd-ihash.kernel.build.install//lib/libhurd-ihash.a' i686-pc-viengoos-gnu-ranlib '[...]/libhurd-ihash.kernel.build.install//lib/libhurd-ihash-nomalloc.a' I'm using the `-C' option -- but that doesn't help much if Automake decides to have ranlib tinker with the files afterwards again. Should this be changed in Automake: to first run ranlib (or whatever else might be done) on them and then install them? Regards, Thomas
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
