From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [btsco] automake error
Date: Tue, 18 Jan 2005 20:56:51 +0100 [thread overview]
Message-ID: <1106078211.8190.79.camel@pegasus> (raw)
In-Reply-To: <41ED434B.9060207@xmission.com>
Hi Brad,
> thanks Luca. keep those patches coming :)
the Debian users should consider to use update-alternatives to choose
their prefered automake. The CVS is for developers and they should know
what they are doing. In a released tarball this doesn't matter anymore.
On the other hand you can simply remove --ignore-deps from the bootstrap
file. I personally don't like this depend stuff and so I don't use it.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-18 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 14:50 [Bluez-devel] [btsco] automake error Luca Capello
2005-01-18 17:11 ` Brad Midgley
2005-01-18 19:56 ` Marcel Holtmann [this message]
2005-01-18 20:10 ` Luca Capello
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=1106078211.8190.79.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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