From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] autoconf breaks portability. Film at 11.
Date: Wed, 12 May 2004 15:48:23 +0200 [thread overview]
Message-ID: <1084369703.25099.56.camel@pegasus> (raw)
In-Reply-To: <1084369122.4426.106.camel@hades.cambridge.redhat.com>
Hi David,
> > I heard of that problem, but I can't reproduce it. If you call
> > "./bootstrap" every that is necessary should be created.
>
> Still no substitute for proper makefiles. Do we _really_ need the system
> to check for itself how to build Fortran shared libraries? Yes, that's
> one of the things it does.
if you can tell me how to disable C++ and Fortran checking I am glad to
include it ;)
> Btw, swave() in hciattach still uses 10 characters of a 9-char array.
Fixed in CVS now.
Regards
Marcel
-------------------------------------------------------
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 prev parent reply other threads:[~2004-05-12 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 9:47 [Bluez-devel] autoconf breaks portability. Film at 11 David Woodhouse
2004-05-12 13:31 ` Marcel Holtmann
2004-05-12 13:38 ` David Woodhouse
2004-05-12 13:48 ` Marcel Holtmann [this message]
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=1084369703.25099.56.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=dwmw2@infradead.org \
/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.