Dan Nicholson wrote:
On Sat, Dec 13, 2008 at 12:57 AM, Jason Curl jcurln...@arcor.de wrote:
Ralf Wildenhues wrote:
Hello Jason,
* Jason Curl wrote on Thu, Dec 11, 2008 at 10:19:57PM CET:
Ignoring that my macro obviously won't work with 2.2.x, I'm using Cygwin
and I've come
Jason Curl wrote:
Dan Nicholson wrote:
On Sat, Dec 13, 2008 at 12:57 AM, Jason Curl jcurln...@arcor.de wrote:
Ralf Wildenhues wrote:
[SNIP]
You're right, I only ran autoreconf. libtoolize fixed the problem.
A concern I have about libtoolize, it copies libtool.m4 and lt*.m4
files to my
Roumen Petrov wrote:
Jason Curl wrote:
Dan Nicholson wrote:
On Sat, Dec 13, 2008 at 12:57 AM, Jason Curl jcurln...@arcor.de
wrote:
Ralf Wildenhues wrote:
[SNIP]
You're right, I only ran autoreconf. libtoolize fixed the problem.
A concern I have about libtoolize, it copies libtool.m4
Ralf Wildenhues wrote:
Hello Jason,
* Jason Curl wrote on Thu, Dec 11, 2008 at 10:19:57PM CET:
Ignoring that my macro obviously won't work with 2.2.x, I'm using Cygwin
and I've come across my first problem. The old libtool is removed
(1.5.27a) and the new is installed (at least I think
Hi Ralf
Ralf Wildenhues wrote:
Hello Jason,
* Jason Curl wrote on Thu, Dec 11, 2008 at 10:19:57PM CET:
Ignoring that my macro obviously won't work with 2.2.x, I'm using Cygwin
and I've come across my first problem. The old libtool is removed
(1.5.27a) and the new is installed (at least
Hello Jason,
* Jason Curl wrote on Sat, Dec 13, 2008 at 09:57:05AM CET:
I for the life of me have no idea how to debug where the macro is coming
from that caused libtool 1.5.26 to be generated. And without that I
can't even begin to explain why I had this problem in the first place.
let's not drop the list from Cc:.
* Jason Curl wrote on Sat, Dec 13, 2008 at 11:39:59AM CET:
Ralf Wildenhues wrote:
Maybe some old in-tree macro files lying around? The macros could have
been copied into m4/* or its contents into acinclude.m4 by somebody or
aclocal.m4 (by aclocal).
On Sat, Dec 13, 2008 at 12:57 AM, Jason Curl jcurln...@arcor.de wrote:
Ralf Wildenhues wrote:
Hello Jason,
* Jason Curl wrote on Thu, Dec 11, 2008 at 10:19:57PM CET:
Ignoring that my macro obviously won't work with 2.2.x, I'm using Cygwin
and I've come across my first problem. The old
Hello,
I got some help with my previous question about library filenames but no
real answer, so I'm looking into what kind of effort it is to move over
to libtool 2.2.6a.
Ignoring that my macro obviously won't work with 2.2.x, I'm using Cygwin
and I've come across my first problem. The old
On Thu, 11 Dec 2008, Jason Curl wrote:
I've removed /usr/share/libtool and reinstalled, but libtool --version always
shows 1.5.27a.
What am I doing wrong?
Libtool is installed to /usr/local/bin by default. Do 'which libtool'
to see which executable/script is being used.
Bob
Hello Jason,
* Jason Curl wrote on Thu, Dec 11, 2008 at 10:19:57PM CET:
Ignoring that my macro obviously won't work with 2.2.x, I'm using Cygwin
and I've come across my first problem. The old libtool is removed
(1.5.27a) and the new is installed (at least I think the old is removed).
I
11 matches
Mail list logo
