Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] libtool and autoconf versions
Date: Wed, 21 Jan 2004 03:10:01 +0100	[thread overview]
Message-ID: <1074651001.7088.64.camel@pegasus> (raw)
In-Reply-To: <1074650832.23181.93.camel@saag>

Hi Edd,

> > what version of libtool and autoconf is used for Debian Woody?
> 
> libtool1.4, autoconf2.53
> 
> >  Do Debian
> > Sarge already uses the new versions?
> 
> sarge (and unstable) have autoconf2.59, libtool1.5

ok, I see. Sarge is on its way becoming stable so it is indeed a good
idea to ship new autoconf and libtool versions with the next tarballs.

Regards

Marcel




-------------------------------------------------------
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

      reply	other threads:[~2004-01-21  2:10 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
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 [this message]

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=1074651001.7088.64.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=edd@usefulinc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox