Peter O'Gorman wrote:
I assume you mean the libtool-1.5 is not available on gnu.org since it
was hacked in March. I believe it's reappearance is waiting on a libtool
admin letting the relevant folks know the md5 checksum for that release.
The checksum I have is 0e1844f25e2ad74c3715b5776d017545
On Thursday, September 11, 2003, at 12:38 AM, Gary V. Vaughan wrote:
The checksum I have is 0e1844f25e2ad74c3715b5776d017545 in case
anyone is interested :)
I am interested :-) Rob rolled that release, and I don't have a
tarball of 1.5 from which to generate the sum myself :-( What date
did
On Wed, 10 Sep 2003, Gary V. Vaughan wrote:
Peter O'Gorman wrote:
I assume you mean the libtool-1.5 is not available on gnu.org since it
was hacked in March. I believe it's reappearance is waiting on a libtool
admin letting the relevant folks know the md5 checksum for that release.
The
On Wed, 10 Sep 2003, Boehne, Robert wrote:
While we're on the subject (sort of) Peter expressed some interest in becoming
a co-maintainer. I think that is a good idea, what about you?
That is something I would like to see as well.
Bob
==
Bob Friesenhahn
Hi Rob, Peter,
Boehne, Robert wrote:
While we're on the subject (sort of) Peter expressed some interest in becoming
a co-maintainer. I think that is a good idea, what about you?
Absolutely! My attention to the libtool lists has been intermittent to say
the least while I am working on m4... and
Bob Friesenhahn [EMAIL PROTECTED] writes:
I have a copy of libtool-1.5.tar.gz which was retrieved on April 15.
The MD5 checksum is also 0e1844f25e2ad74c3715b5776d017545.
I have a copy dated April 14 with the same MD5 checksum.
--
Russ Allbery ([EMAIL PROTECTED])
Hello.
Bob Friesenhahn wrote:
On Wed, 10 Sep 2003, Gary V. Vaughan wrote:
[snip]
I am interested :-) Rob rolled that release, and I don't have a tarball
of 1.5 from which to generate the sum myself :-( What date did you
download it? Hopefully, very soon after the upload judging by the
[EMAIL PROTECTED] wrote:
Hi,
I'm swimming in a libiconv protage on QNX and I have a problem with shared
library namming.
First, the original configure script in libiconv-1.9.1 doesn't know the
QNX
platform.
After some discussions with a QNX people, I got the informations to
rebuild
all the
On Tuesday, September 9, 2003, at 8:41 PM, [EMAIL PROTECTED]
wrote:
That means I have a dependancy problem but I don't know what to
update. I wanted
to try libtool-1.5 but it that's a simple ghost!!
I assume you mean the libtool-1.5 is not available on gnu.org since it
was hacked in March. I
[EMAIL PROTECTED] wrote:
Hi Max,
Sorry for the mistake but in fact I invoke libtoolize -f -c' and
'automake-1.7 -a -c '!
Anyway, I get a new ltmain.sh, the one is stored in my libtool (1.4.3)
directory.
So, either ltmain.sh is bad in libtool-1.4.3 (I don't think so) or the
source
file
[EMAIL PROTECTED] wrote:
Ok, Ok Max.
Now I remember also that I had to do 'aclocal-1.7 -I ./m4 ...' and
according
to the libiconv developper, he use slightly modified libtool1.5 files.
That's
the reason why I get a serial 47.
So, I suppose I have to update aclocal and automake to maybe 1.8
11 matches
Mail list logo
