From: David Woodhouse <dwmw2@infradead.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] autoconf breaks portability. Film at 11.
Date: Tue, 11 May 2004 10:47:13 +0100 [thread overview]
Message-ID: <1084268833.11301.0.camel@hades.cambridge.redhat.com> (raw)
I cannot build libs2. The autoconf stuff is broken. The last thing it
says is this:
configure.in:19: required file `./ltmain.sh' not found
Please can we ditch this crap and use sane makefiles instead?
--
dwmw2
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-05-11 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 9:47 David Woodhouse [this message]
2004-05-12 13:31 ` [Bluez-devel] autoconf breaks portability. Film at 11 Marcel Holtmann
2004-05-12 13:38 ` David Woodhouse
2004-05-12 13:48 ` Marcel Holtmann
2004-05-12 14:11 ` David Woodhouse
2004-05-12 17:23 ` Marcel Holtmann
2004-05-12 18:03 ` David Woodhouse
2004-05-12 21:46 ` Marcel Holtmann
2004-05-13 6:53 ` David Woodhouse
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=1084268833.11301.0.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.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