From: David Woodhouse <dwmw2@infradead.org>
To: Marcel Holtmann <marcel@holtmann.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:11:29 +0100 [thread overview]
Message-ID: <1084371089.4426.148.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <1084369703.25099.56.camel@pegasus>
On Wed, 2004-05-12 at 15:48 +0200, Marcel Holtmann wrote:
> if you can tell me how to disable C++ and Fortran checking I am glad to
> include it ;)
I sent you proper Makefiles a long time ago. You didn't apply them :)
This is what I get on Fedora Core 2 on both i386 and PPC, btw:
hades /hades/bluez/libs2 $ ./bootstrap
configure.in: installing `./install-sh'
configure.in: installing `./missing'
configure.in:19: installing `./config.guess'
configure.in:19: installing `./config.sub'
configure.in:19: required file `./ltmain.sh' not found
compat/Makefile.am: installing `./depcomp'
> > Btw, swave() in hciattach still uses 10 characters of a 9-char array.
>
> Fixed in CVS now.
OK, you can have another one then :)
On PPC, the HCI/LMP version numbers and manufacturer code are
byte-swapped in hciconfig from utils2. hciconfig from bluez-utils-2.7
gives:
HCI Ver: 1.2 (0x2) HCI Rev: 0x4d9 LMP Ver: 1.2 (0x2) LMP Subver: 0x4d9
Manufacturer: Cambridge Silicon Radio (10)
... while hciconfig from utils2 gives:
HCI Ver: 1.2 (0x2) HCI Rev: 0xd904 LMP Ver: 1.2 (0x2) LMP Subver: 0xd904
Manufacturer: not assigned (2560)
--
dwmw2
next prev parent reply other threads:[~2004-05-12 14:11 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
2004-05-12 14:11 ` David Woodhouse [this message]
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=1084371089.4426.148.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox