Debian Bug report logs - #13730
dpkg uses outdated libtool

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: adam@yggdrasil.com (Adam J. Richter)

To: submit@bugs.debian.org

Cc: klee@debian.org, tromey@creche.cygnus.com

Subject: dpkg uses outdated libtool

Date: Wed, 8 Oct 1997 16:59:22 -0700 (PDT)

Package:	dpkg
Version:	1.4.0.19

	ftp://ftp.debian.org/debian/project/experimental/dpkg-1.4.0.19.tar.gz

	At the outset, let me thank Tom Tromey at Cygnus for
pointing me in the right direction on this.  At first I thoght this
was an automake bug, but it is really a dpkg bug, or rather a case of
the latest dpkg not being compatable with the latest automake.

	dpkg is distributed with an older version of libtool
and ltconfig, which automake-1.2 does not detect.  This results in
automake not exapnding the AM_PROG_LIBTOOL macro in the supplied
configure.in.

	I believe that the correct solution is:

		o Document that dpkg requires libtool and that libtool
		  is available from ftp://prep.ai.mit.edu/pub/gnu/.
		o Remove the old libtool and ltconfig.sh from the dpkg
	          source, and adjust the Makefiles to use the installed
		  libtool in /usr/bin and ltconfig.sh in /usr/share/libtool.

	For further reference, I have attached my original trouble report
along with Tom's informative response.  Feel free to get in touch with
me if you have any other questions.

Adam J. Richter     __     ______________   4880 Stevens Creek Blvd, Suite 205
adam@yggdrasil.com     \ /                  San Jose, California 95129-1034
+1 408 261-6630         | g g d r a s i l   United States of America
fax +1 408 261-6631      "Free Software For The Rest Of Us."


>From creche.cygnus.com!tromey Mon Oct  6 23:25:08 1997
>To: adam@yggdrasil.com (Adam J. Richter)
>Cc: automake-bugs@gnu.org, klee@debian.org
>Subject: Re: aclocal-1.2 does not define AM_PROG_LIBTOOL
>References: <m0xIO3P-0001APC@adam.yggdrasil.com>
>X-Zippy:  If our behavior is strict, we do not need fun!
>X-Attribution:  Tom
>BCC:
>Reply-To: tromey@cygnus.com
>From: Tom Tromey <tromey@creche.cygnus.com>
>Date: 07 Oct 1997 00:28:39 -0600
>In-Reply-To: adam@yggdrasil.com's message of Mon, 6 Oct 1997 18:03:15 -0700 (PDT)
>Lines: 16
>X-Mailer: Red Gnus v0.34/Emacs 19.34

>Adam> It appears that aclocal-1.2 does not define AM_PROG_LIBTOOL
>Adam> macro in the aclocal.m4 file that it generates.

>You have to have libtool installed before this will work.

>AM_PROG_LIBTOOL isn't included in automake because automake and
>libtool have different maintainers, and coordinating releases is too
>painful.


>It is a bug in a sense -- aclocal should probably at least mention
>that it can't find AM_PROG_LIBTOOL.

>Tom
>-- 
>tromey@cygnus.com                 Member, League for Programming Freedom

Re: aclocal-1.2 does not define AM_PROG_LIBTOOL

Message #10 received at 13730@bugs.debian.org (full text, mbox, reply):

From: Klee Dienes <klee@mit.edu>

To: adam@yggdrasil.com (Adam J. Richter), 13730@bugs.debian.org

Subject: Re: dpkg uses outdated libtool

Date: Sun, 02 Nov 1997 22:12:54 -0500

Hi.  Sorry to take so long to respond to your message.  I was out of
town for several weeks for a family medical emergency, and am just now
catching up on my E-mail.

You made two suggestions:

> 		o Document that dpkg requires libtool and that libtool
> 		  is available from ftp://prep.ai.mit.edu/pub/gnu/.

I've done this for the next revision, by including a document for
those who intend to run the 'maintainer-only' targets.

> 		o Remove the old libtool and ltconfig.sh from the dpkg
> 	          source, and adjust the Makefiles to use the installed
> 		  libtool in /usr/bin and ltconfig.sh in /usr/share/libtool.

Much as I like this idea, I'm actually moving away from it in future
versions of dpkg, because I'd like to make sure dpkg is highly
portable to systems without much GNU software, and in particular to
systems other than Linux.

To do this, I've been working to make the dpkg source package depend
on only those system utilities permitted by the GNU coding standards.
(I've even started including parts of libiberty, for systems without a
complete C library).  The intent is that one should be able to build
and install a dpkg distribution with no other GNU tools available,
(especially libtool and automake, which tend to still be a bit
unstable these days).

You're definitely right that I should document the procedure for
re-running automake and libtool a bit better, though.  I've tried to
do this for the next revision.  For the moment, examining the
'configure' target in 'debian/rules' may be useful.

Please be sure to let me know if you're having any trouble building or 
installing dpkg, and I'll do my best to help.

Thanks,
 - Klee

Message #15 received at 13730@bugs.debian.org (full text, mbox, reply):

From: Yann Dirson <dwitch@monge.univ-mlv.fr>

To: Klee Dienes <klee@mit.edu>, 13730@bugs.debian.org

Subject: Re: Bug#13730: dpkg uses outdated libtool

Date: Fri, 7 Nov 1997 18:58:45 +0100

Klee Dienes writes:
 > Much as I like this idea, I'm actually moving away from it in future
 > versions of dpkg, because I'd like to make sure dpkg is highly
 > portable to systems without much GNU software, and in particular to
 > systems other than Linux.
 > 
 > To do this, I've been working to make the dpkg source package depend
 > on only those system utilities permitted by the GNU coding standards.
 > (I've even started including parts of libiberty, for systems without a
 > complete C library).  The intent is that one should be able to build
 > and install a dpkg distribution with no other GNU tools available,
 > (especially libtool and automake, which tend to still be a bit
 > unstable these days).

I'm not sure I get your point here. Just like it is with autoconf,
automake (1.2) and libtool (1.0c) just aren't required to compile a
distribution (as long as the distribution is well-behaved in this
respect, which I could verify 1.4.0.21 was not; I think I already told
you that, some monthes ago).

That being said, I don't see the point of moving away from
automake/libtool, apart from the fact that there're not mature right
now.

Am I missing something ?
-- 
Yann Dirson  <ydirson@a2points.com>      | Stop making M$-Bill richer & richer,
alt-email:     <dirson@univ-mlv.fr>      |     support Debian GNU/Linux:
debian-email:   <dirson@debian.org>      |         more powerful, more stable !
http://www.a2points.com/homepage/3475232 |
                    -----------------------------------------
                    A computer engineer's looking for a job !
                    -----------------------------------------

Message #20 received at 13730@bugs.debian.org (full text, mbox, reply):

From: Klee Dienes <klee@mit.edu>

To: Yann Dirson <dirson@univ-mlv.fr>, 13730@bugs.debian.org

Subject: Re: Bug#13730: dpkg uses outdated libtool

Date: Fri, 07 Nov 1997 16:46:41 -0500

Yann Dirson writes:

> Klee Dienes writes:
>> Much as I like this idea, I'm actually moving away from it in future
>> versions of dpkg, because I'd like to make sure dpkg is highly
>> portable to systems without much GNU software, and in particular to
>> systems other than Linux.
>
> That being said, I don't see the point of moving away from
> automake/libtool, apart from the fact that there're not mature right
> now.

Sorry, I wasn't clear.  I meant to say:

I'm moving away from having the debian/rules file run
aclocal/libtoolize/automake, and instead plan to distribute the Debian
source package as a single GNU-format source archive with the
Makefile.in, configure, and info files already generated.

I've no plans at all to move away from autoconf/libtool/automake as a
whole, though I must admit I've been sorely tempted several times in
the past.  :-).

> respect, which I could verify 1.4.0.21 was not; I think I already told
> you that, some monthes ago).

Yep, you did --- it's fixed in 1.4.1.3, which I'll be uploading as
soon as I finish off a couple more nagging Rhapsody-related bugs.

Message #25 received at 13730@bugs.debian.org (full text, mbox, reply):

From: Ian Jackson <ian@davenant.greenend.org.uk>

To: 13730@bugs.debian.org

Subject: Bug#13730: dpkg uses outdated libtool

Date: Sat, 8 Nov 1997 14:51:18 +0000

Klee writes:
> I'm moving away from having the debian/rules file run
> aclocal/libtoolize/automake, and instead plan to distribute the Debian
> source package as a single GNU-format source archive with the
> Makefile.in, configure, and info files already generated.

Oh, good !  This may fix my recent bug report (I haven't had the ack
back yet, so I don't have the number) about debian/rules clean failing
because I'd run configure in the source tree rather than in
debian/build.  I think this debian/build business is asking for
trouble.

Ian.

Message #30 received at 13730@bugs.debian.org (full text, mbox, reply):

From: Ben Collins <bcollins@debian.org>

To: control@bugs.debian.org

Subject: reassigning fixed bugs for dpkg

Date: Thu, 21 Oct 1999 13:50:11 -0400

# These bugs are being reassigned to dpkg-iwj. What this means is that
# they have been fixed in the primary dpkg contained in the potato
# archive, but have not been merged upstream. Please take the time to
# assure that your bug was actually fixed, and reassign it back to dpkg if
# it was not.
#
# Thanks,
#   Ben

reassign 42239 dpkg-iwj
reassign 1921 dpkg-iwj
reassign 26431 dpkg-iwj
reassign 4801 dpkg-iwj
reassign 32637 dpkg-iwj
reassign 5536 dpkg-iwj
reassign 13730 dpkg-iwj
reassign 26432 dpkg-iwj
reassign 24309 dpkg-iwj
reassign 45739 dpkg-iwj
reassign 33086 dpkg-iwj
reassign 7128 dpkg-iwj
reassign 14663 dpkg-iwj
reassign 15017 dpkg-iwj
reassign 13929 dpkg-iwj
reassign 34642 dpkg-iwj
reassign 31784 dpkg-iwj
reassign 24472 dpkg-iwj
reassign 46808 dpkg-iwj
reassign 19038 dpkg-iwj
reassign 22351 dpkg-iwj
reassign 22748 dpkg-iwj
reassign 25653 dpkg-iwj
reassign 31256 dpkg-iwj
reassign 32031 dpkg-iwj
reassign 39420 dpkg-iwj
reassign 35117 dpkg-iwj
reassign 33347 dpkg-iwj
reassign 37810 dpkg-iwj

# misc. cleanups
severity 33344 wishlist
merge 30126 33263
close 44654

stop

Send a report that this bug log contains spam.