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 library. But I can only do this if you have
On 9/10/13, Peter Rosin p...@lysator.liu.se 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...
Anyway, does
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 09:47, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se 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
On 9/10/13, Peter Rosin p...@lysator.liu.se 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 in
when
*** you link
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 10:55, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 09:47, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 09:08, Ozkan Sezer wrote:
Tell me if you need
On 9/10/13, Ozkan Sezer seze...@gmail.com wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se 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 provide the output from libtool --config
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 11:26, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 10:55, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 09:47, Ozkan Sezer wrote:
On 9/10/13, Peter
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 15:00, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se 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
On 9/10/13, Ozkan Sezer seze...@gmail.com wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 11:26, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09-10 10:55, Ozkan Sezer wrote:
On 9/10/13, Peter Rosin p...@lysator.liu.se wrote:
On 2013-09
On 9/11/13, Peter Rosin p...@lysator.liu.se 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.org/archive/html/libtool/2013-09/index.html
On Wed, Sep 11, 2013 at 1:32 PM, Ozkan Sezer seze...@gmail.com wrote:
On 9/11/13, Peter Rosin p...@lysator.liu.se 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
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
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
On Fri, Dec 6, 2013 at 10:11 AM, Peter Rosin p...@lysator.liu.se 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
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
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
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
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
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
>>
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
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?
On 11/16/20, Ryan Schmidt wrote:
> Duplicate of #44605.
Be that as it may, but this #44684 has, as it seems, a sensible
patch. Shall no one review it?
Commit f54924fa5d8d5959038e58adab7c552c3ca495ae seems to have been
wrongly applied.
Regards.
--
O.S.
From e84eddb8b98fee7a31d95bb1b8e701f5ef3dca50 Mon Sep 17 00:00:00 2001
From: Ozkan Sezer
Date: Fri, 1 Mar 2024 11:37:28 +0300
Subject: [PATCH] ltmain.in: correct windows compiler preprocessor
23 matches
Mail list logo
