From: Edd Dumbill <edd@usefulinc.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] libtool and autoconf versions
Date: Tue, 20 Jan 2004 21:05:09 +0000 [thread overview]
Message-ID: <1074632708.23181.56.camel@saag> (raw)
In-Reply-To: <1074632525.1707.181.camel@localhost>
On Tue, 2004-01-20 at 21:02, Max Krasnyansky wrote:
> I'd say lets update.
> btw What exactly depends on the old autoconf ? I mean if you just run
> ./bootstrap on the machine that has new version it just works right.
> At least it does on Fedora with the latest au
I'm talking about what's shipped in the tarballs, which uses
libtool1.4. Packagers for distros rely on the tarball releases. In the
(admittedly) unlikely event that changes need to be made and autoconf
re-run for the purposes of packaging, the old ac and libtool would be
needed.
-- Edd
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-01-20 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 11:11 [Bluez-devel] libtool and autoconf versions Edd Dumbill
2004-01-20 21:02 ` Max Krasnyansky
2004-01-20 21:05 ` Edd Dumbill [this message]
2004-01-20 21:10 ` Max Krasnyansky
2004-01-21 1:53 ` Marcel Holtmann
2004-01-21 2:07 ` Edd Dumbill
2004-01-21 2:10 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074632708.23181.56.camel@saag \
--to=edd@usefulinc.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.