From: Johan Hedberg <johan.hedberg@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Build failure for bluez-hcidump
Date: Mon, 20 Jun 2011 12:15:08 +0300 [thread overview]
Message-ID: <20110620091508.GA7447@dell.ger.corp.intel.com> (raw)
In-Reply-To: <1308560171.6042.3.camel@novo.hadess.net>
Hi Bastien,
On Mon, Jun 20, 2011, Bastien Nocera wrote:
> bluez-hcidump 2.1 fails to build on Fedora 16:
>
> src/hcidump.c: In function 'process_frames':
> src/hcidump.c:313:5: warning: implicit declaration of function 'hton64' [-Wimplicit-function-declaration]
> src/hcidump.c: In function 'read_dump':
> src/hcidump.c:430:4: warning: implicit declaration of function 'ntoh64' [-Wimplicit-function-declaration]
> CCLD src/hcidump
> src/hcidump.o: In function `process_frames':
> /builddir/build/BUILD/bluez-hcidump-2.1/src/hcidump.c:313: undefined reference to `hton64'
> src/hcidump.o: In function `read_dump':
> /builddir/build/BUILD/bluez-hcidump-2.1/src/hcidump.c:436: undefined reference to `ntoh64'
> /builddir/build/BUILD/bluez-hcidump-2.1/src/hcidump.c:430: undefined reference to `ntoh64'
>
> Both i686 and x86-64 fails to build with the same error.
>
> http://koji.fedoraproject.org/koji/getfile?taskID=3143039&name=build.log
> shows the full build log.
Those functions have been part of bluetooth.h since bluez 4.90 (released
in March this year). Seems like hcidump is missing proper checks for
them.
Johan
prev parent reply other threads:[~2011-06-20 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 8:56 Build failure for bluez-hcidump Bastien Nocera
2011-06-20 9:15 ` Johan Hedberg [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=20110620091508.GA7447@dell.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).