Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, JonY <10wa...@gmail.com> wrote: > On 9/10/2013 02:12, Ozkan Sezer wrote: >> >> *** Warning: linker path does not have real file for library -lole32. >> *** I have the capability to make that library automatically link in when >> *** you link to this li

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 12:52, Ozkan Sezer wrote: >> That effectively cripples libtool for cross-compilers. Can the behavior >> be refined instead? Can you contact Charles Wilson about this? > > He should be reading this list, if he has time... >

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 09:47, Ozkan Sezer wrote: >> On 9/10/13, Peter Rosin wrote: >>> On 2013-09-10 09:08, Ozkan Sezer wrote: >>>> Tell me if you need anything else. >>> >>> Let's focus on the libtool 2.4.2.393-5d4a i

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 00:34, JonY wrote: >> On 9/10/2013 02:12, Ozkan Sezer wrote: >>> >>> *** Warning: linker path does not have real file for library -lole32. >>> *** I have the capability to make that library automatically link

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 10:55, Ozkan Sezer wrote: >> On 9/10/13, Peter Rosin wrote: >>> On 2013-09-10 09:47, Ozkan Sezer wrote: >>>> On 9/10/13, Peter Rosin wrote: >>>>> On 2013-09-10 09:08, Ozkan Sezer wrote: >>>&g

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Ozkan Sezer wrote: > On 9/10/13, Peter Rosin wrote: >> On 2013-09-10 09:08, Ozkan Sezer wrote: >>> Tell me if you need anything else. >> >> Let's focus on the libtool 2.4.2.393-5d4a if that's ok with >> you. >> >> Can you pr

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 11:26, Ozkan Sezer wrote: >> On 9/10/13, Peter Rosin wrote: >>> On 2013-09-10 10:55, Ozkan Sezer wrote: >>>> On 9/10/13, Peter Rosin wrote: >>>>> On 2013-09-10 09:47, Ozkan Sezer wrote: >>>>

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 15:00, Ozkan Sezer wrote: >> On 9/10/13, Peter Rosin wrote: >>> On 2013-09-10 12:52, Ozkan Sezer wrote: >>>> That effectively cripples libtool for cross-compilers. Can the behavior >>>> be refined instead?

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Ozkan Sezer wrote: > On 9/10/13, Peter Rosin wrote: >> On 2013-09-10 11:26, Ozkan Sezer wrote: >>> On 9/10/13, Peter Rosin wrote: >>>> On 2013-09-10 10:55, Ozkan Sezer wrote: >>>>> On 9/10/13, Peter Rosin wrote: >>>>>

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: [...] >> @@ -2416,10 +2416,22 @@ >>sys_lib_search_path_spec="$sys_lib_search_path_spec >> /usr/lib/w32api"]) >>;; >> mingw* | cegcc*) >># MinGW DLLs use traditional 'lib' prefix >>soname_spec='$libname`echo $release | $SED -e >> '

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Ozkan Sezer wrote: > On 9/10/13, Peter Rosin wrote: > [...] >>> @@ -2416,10 +2416,22 @@ >>>sys_lib_search_path_spec="$sys_lib_search_path_spec >>> /usr/lib/w32api"]) >>>;; >>> mingw* |

Re: libtool woes

2013-09-10 Thread Ozkan Sezer
On 9/10/13, Peter Rosin wrote: > On 2013-09-10 15:29, Ozkan Sezer wrote: >> On 9/10/13, Peter Rosin wrote: >>> On 2013-09-10 15:00, Ozkan Sezer wrote: >>>> On 9/10/13, Peter Rosin wrote: >>>>> On 2013-09-10 12:52, Ozkan Sezer wrote: >>>>

Re: libtool woes

2013-09-11 Thread Ozkan Sezer
On 9/11/13, Peter Rosin wrote: > On 2013-09-10 16:10, Peter Rosin wrote: >> On 2013-09-10 15:56, Ozkan Sezer wrote: >>> OK then, I'll keep an eye on mails from this list. >>> >>> (On an irrelevant note, the archive pages at >>> http://lists.gnu.or

Re: libtool woes

2013-09-17 Thread Ozkan Sezer
On Wed, Sep 11, 2013 at 1:32 PM, Ozkan Sezer wrote: > On 9/11/13, Peter Rosin wrote: >> On 2013-09-10 16:10, Peter Rosin wrote: >>> On 2013-09-10 15:56, Ozkan Sezer wrote: >>>> OK then, I'll keep an eye on mails from this list. >>>> >>>

bootstrap breakage starting with fec7d87

2013-11-06 Thread Ozkan Sezer
Starting with fec7d87 ("funclib.sh: simplify version comparison functions") I am getting the following error from bootstrap: bootstrap: error: 'makeinfo' version == 4.13 is too old bootstrap:'makeinfo' version >= 4.8 is required 9fd7b88 is fine. This is with Fedora 16, with grep-

Re: bootstrap breakage starting with fec7d87

2013-11-19 Thread Ozkan Sezer
> Starting with fec7d87 ("funclib.sh: simplify version comparison > functions") I am getting the following error from bootstrap: > > bootstrap: error: 'makeinfo' version == 4.13 is too old > bootstrap:'makeinfo' version >= 4.8 is required > > 9fd7b88 is fine. > > This is with Fedora

Re: git commit forces bootstrap

2013-12-06 Thread Ozkan Sezer
On Fri, Dec 6, 2013 at 10:11 AM, Peter Rosin wrote: > Hi! > > In my setup, I have to rerun "./bootstrap -fc" after every commit I make > to my local git libtool repo, which is very annoying. If I forget, and > simply type make, configure runs (I can live with that), but after that > I get this out

status of the os2 patches

2014-01-03 Thread Ozkan Sezer
Will the os2 patches posted by KO Myung-Hun back in november 2011 (links below) be merged mainline? http://lists.gnu.org/archive/html/libtool-patches/2012-11/msg4.html http://lists.gnu.org/archive/html/libtool-patches/2012-11/msg5.html http://lists.gnu.org/archive/html/libtool-patches/2012

Re: New release with OSX Yosemite fix?

2014-10-23 Thread Ozkan Sezer
On 10/23/14, Gary V. Vaughan wrote: >> On 23 Oct 2014, at 15:06, Volker Braun wrote: >> >> Is there any chance for cutting a new release with the OSX Yosemite >> version parsing fix? This is going to affect a lot of users, and right >> now there isn't even a released version of libtools to run re

Re: [RFC] any critical patches for a release this weekend?

2014-10-23 Thread Ozkan Sezer
> On Oct 23, 2014, at 3:10 PM, Gary V. Vaughan wrote: > > I plan to roll a release based off the v2.4.2 tag, incorporating fixes > for version mismatches against Mac OS Yosemite this weekend - in > consideration of the fact that there are still known regressions in > master. > > If there's anythin

Re: New libtool maintainer

2021-11-20 Thread Ozkan Sezer
On 10/27/21, Alex Ameen wrote: > Howdy! > > This is Alex Ameen reporting in from Austin, Texas. I'm a long time GNU > and `autotools' user who specializes in ELF linking and loading. I'm > writing you today to introduce myself and announce that I was recently > approved as the new maintainer of `l

Re: disable invocation of winepath by libtool

2021-12-06 Thread Ozkan Sezer
On 12/5/21, ilya Basin wrote: > Dear List. I'm cross compiling a program on Linux for a mingw host and > sometimes this shows Wine dialogs like "updating wine configuration" or > "download and install Mono". I believe it's only needed to run `make check` > successfully, but I want to skip the test

Re: New libtool maintainer

2022-02-07 Thread Ozkan Sezer
On 2/8/22, Julien ÉLIE wrote: > Hi Alex, > >> Feel free to reach out if you have pending patches/issues you want to >> "bump", ideas for improvements, general advice for a new GNU maintainer >> - and above all if you'd like to lend a hand toward getting `libtool' up >> and running again. > > Many

Re: New libtool maintainer

2022-02-08 Thread Ozkan Sezer
On 2/8/22, Roumen Petrov wrote: > As result is expected Debian to be flooded with defects. > >> Some of the outstanding bugs with existing patches : >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38305 >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23348 >> https://debbugs.gnu.org/cgi/bugrepor

Re: Introducing a new maintainer of libtool

2024-01-17 Thread Ozkan Sezer
Please remember to check with debbugs.gnu.org: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=libtool;max-bugs=100;base-order=1;bug-rev=1 There are plenty of bugs in there. E.g.: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=45738 https://deb

Re: Introducing a new maintainer of libtool

2024-01-18 Thread Ozkan Sezer
On 1/18/24, Mike Frysinger wrote: > On 17 Jan 2024 20:07, Ozkan Sezer wrote: [...] >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=52253 > > doesn't look like a regression. it can wait. It's a regression from 2.2.6, later versions have the issue, so how is it not a regression?

Re: [sr #111069] libtool: patch: Fix dynamic_lookup warnings from new Mac linker

2024-06-21 Thread Ozkan Sezer
> I have merged a patch in the development branch to append '-no_fixup_chains' > for macOS versions 11.3*-14* and Xcode versions 13-15*. I have verified this > removes the warning that I was seeing on macOS 12.7.5, Xcode > 14.2.0.0.1.1668646533 [1][2]. I have not seen any regressions from this on >

Re: [sr #111069] libtool: patch: Fix dynamic_lookup warnings from new Mac linker

2024-06-27 Thread Ozkan Sezer
On Thu, Jun 27, 2024 at 5:29 PM Ileana Dumitrescu wrote: > > Follow-up Comment #16, sr #111069 (group libtool): > > I have updated development with a feature test: > > https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=3d1baeeef90a6b9e16c545babe833f28dca155a7 > > Please tell me

Re: -no_fixup_chains patch

2024-06-27 Thread Ozkan Sezer
[Sorry, I seem to have deleted the mailing list message from my inbox] Regarding -no_fixup_chains patch i.e. http://git.savannah.gnu.org/gitweb/?p=libtool.git;a=commitdiff;h=3d1baeeef90a6b9e16c545babe833f28dca155a7 Is '+=' universally supported?? Maybe change to something like the following??

[PATCH] fix appending of -no_fixup_chains to _lt_dar_allow_undefined

2024-06-29 Thread Ozkan Sezer
undefined='$_lt_dar_allow_undefined $wl-no_fixup_chains' +_lt_dar_allow_undefined='$wl-undefined ${wl}dynamic_lookup $wl-no_fixup_chains' + else +_lt_dar_allow_undefined='$wl-undefined ${wl}dynamic_lookup' fi ;; esac From 6bf0

Re: -no_fixup_chains patch

2024-07-03 Thread Ozkan Sezer
On Wed, Jul 3, 2024 at 6:42 PM Ileana Dumitrescu wrote: > > On 02/07/2024 22:01, Václav Haisman wrote: > > On 28. 06. 24 0:41, Ozkan Sezer wrote: > >> [Sorry, I seem to have deleted the mailing list message from my inbox] > >> > >> Regarding -no

Re: -no_fixup_chains patch

2024-07-04 Thread Ozkan Sezer
On Thu, Jul 4, 2024 at 4:54 PM Ileana Dumitrescu wrote: > > On 03/07/2024 21:28, Ozkan Sezer wrote: > > On Wed, Jul 3, 2024 at 6:42 PM Ileana Dumitrescu > > wrote: > > However, if you guys do this: AS_VAR_APPEND requires autoconf 2.64. What > > is the minimum