I noticed the typo occured in a generated libtool script. It turns
out this has already been corrected in libtool CVS HEAD, but similar
typos exists elsewhere in libtool: occured in the documentation should
be occurred, and occurence in a code comment should be occurrence.
Patch against CVS
On Wed, Jun 01, 2005 at 09:16:38PM +0200, Ralf Wildenhues wrote:
* Olly Betts wrote on Sun, May 29, 2005 at 02:45:28AM CEST:
Patch against CVS HEAD.
Well, turns out that patch is against branch-1-5, [...]
Oops, you're right of course. I just used a CVS libtool tree I had
lying around from
On 2005-09-14, Ralf Wildenhues [EMAIL PROTECTED] wrote:
--- libltdl/argz.c1 Jun 2005 19:09:00 - 1.5
+++ libltdl/argz.c14 Sep 2005 15:56:38 -
@@ -29,6 +29,7 @@
/* Provide our wierdo HAVE_CONFIG_H rvalue for other clients. */
#if !defined(LTDL)
I noticed that the sed and grep combination in func_lalib_p can be
folded into a single use of sed. I don't think this is likely to
be a hot spot, but it's an easy fix.
I'm not an expert on sed portability but it doesn't seem to fall afoul
of anything in the autoconf manual.
The patch is
On 2008-04-24, Ralf Wildenhues [EMAIL PROTECTED] wrote:
* Olly Betts wrote on Thu, Apr 24, 2008 at 08:04:03AM CEST:
I noticed that the sed and grep combination in func_lalib_p can be
folded into a single use of sed. I don't think this is likely to
be a hot spot, but it's an easy fix.
I'm
On 2008-05-07, Gary V. Vaughan [EMAIL PROTECTED] wrote:
+ - New lt_dloadvise_preload() call to set a hint that only preloadeded
I think lt_dloadvise_preload should be lt_dladvise_preload.
Cheers,
Olly
On 2008-05-25, Charles Wilson [EMAIL PROTECTED] wrote:
+#define LTWRAPPER_OPTION_PREFIX --lt-
+#define LTWRAPPER_OPTION_PREFIX_LENGTH 5
If the idea is that the user can change LTWRAPPER_OPTION_PREFIX, then
hard-coding the length risks a mismatch if they fail to update
On 2010-06-18, Charles Wilson libt...@cwilson.fastmail.fm wrote:
b3) For these reasons, it's probably best if the package
maintainer also provides rules for embedding the manifest
in binary form into the real exe. How these rules will
deal with the whole lt-*.exe
On 2010-06-23, Jirka Hladky jhla...@redhat.com wrote:
we have run into a problem where package developed on Debian and packaged for
Fedora had rpath included in binaries. This is bad and forbidden by rpm rules
(rpmlint will mark it as an error).
After long discussion with upstream and
Using -Fe instead of -o avoids the warning and should be OK with older
versions too (the MSVS 2008 docs list -Fe).
Cheers,
Olly
From 0d1a97460cf14d2574db4749f7bf4c2145035c07 Mon Sep 17 00:00:00 2001
From: Olly Betts <o...@survex.com>
Date: Wed, 24 Jan 2018 14:09:23 +1300
Subject: [PATC
On 2018-01-24, Josh Soref <jso...@gmail.com> wrote:
> Olly Betts wrote:
> > Using -Fe instead of -o avoids the warning and should be OK with older
> > versions too (the MSVS 2008 docs list -Fe).
>
> That flag is much older than 2008.
>
> https://msdn.microsoft.c
mments:
---
Date: Mon 27 Nov 2023 03:53:22 AM UTC By: Olly Betts
Use -Fe with MSVC to specify DLL output filename
This avoids a deprecation warning with current versions of MSVC, and is
documented as supported at least as far back as Visual C 6.0 which was
released i
Follow-up Comment #1, patch #9996 (group libtool):
It looks like that patch was merged in 2021
(9e8c882517082fe5755f2524d23efb02f1522490) and was included in libtool 2.4.7.
___
Reply to this item at:
13 matches
Mail list logo