Re: [PATCH] Correct typo: $sharedlib_from_linklib_cmd missing '_cmd'

Den 2010-09-11 07:02 skrev Charles Wilson: OK to push as obvious? To me, pushing as obvious is the same as pushing without asking (and when I do, I make damn sure I don't push anything bad). This makes me curious, what does it mean to you? Cheers, Peter

Re: [PATCH] Correct typo: $sharedlib_from_linklib_cmd missing '_cmd'

Hi Charles, * Charles Wilson wrote on Sat, Sep 11, 2010 at 07:02:29AM CEST: * libltdl/config/ltmain.m4sh (func_generate_dlsyms): Fix obvious typo, $sharedlib_from_linklib_cmd missing '_cmd'. --- Typo in e83da49a1faf9df1c7e351df9e9b175388d76619: there is no variable named

Re: [PATCH 7/7] Prefer $NM @file over calculating the cmd line length.

Den 2010-09-08 21:29 skrev Ralf Wildenhues: I guess I'm a bit put off by this patch in that it makes it harder on GNU/Linux to debug libtool by copying and pasting the commands that it outputs, because the response file will be invisible. On this system, there's no advantage as long as the

Re: [PATCH] Correct typo: $sharedlib_from_linklib_cmd missing '_cmd'

On 9/11/2010 2:47 AM, Peter Rosin wrote: Den 2010-09-11 07:02 skrev Charles Wilson: OK to push as obvious? To me, pushing as obvious is the same as pushing without asking (and when I do, I make damn sure I don't push anything bad). This makes me curious, what does it mean to you? It means

Re: [PATCH] Correct typo: $sharedlib_from_linklib_cmd missing '_cmd'

On 9/11/2010 4:16 AM, Ralf Wildenhues wrote: OK to push. Pushed. -- Chuck

Re: [PATCH] Correct typo: $sharedlib_from_linklib_cmd missing '_cmd'

On 09/11/2010 10:09 AM, Charles Wilson wrote: On 9/11/2010 2:47 AM, Peter Rosin wrote: Den 2010-09-11 07:02 skrev Charles Wilson: OK to push as obvious? To me, pushing as obvious is the same as pushing without asking (and when I do, I make damn sure I don't push anything bad). This makes me

[PATCH] * HACKING (Maintenance Notes): Adjust to moved files.

Hi! I noticed that HACKING referred to files that have been moved. Should I also add libltdl/config/compile? But that one does not appear to be handled by make -fMakefile.maint fetch. Shouldn't it? Which 'compile' will be bundled with libtool if libtool is released before an automake is released

libtool does not recognize lib64 -- Update to Olly Betts' patch

Greetings. I package software for Fedora and frequently get hit with /usr/lib64 being added as an rpath in builds. I found what I think is the last thread on this subject here: http://lists.gnu.org/archive/html/libtool-patches/2010-06/msg00141.html In the second message, Olly Betts links to a

Re: [PATCH] * HACKING (Maintenance Notes): Adjust to moved files.

* Peter Rosin wrote on Sat, Sep 11, 2010 at 09:02:54PM CEST: I noticed that HACKING referred to files that have been moved. Should I also add libltdl/config/compile? Yes, plase. But that one does not appear to be handled by make -fMakefile.maint fetch. Shouldn't it? It should. Thanks.