Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Trouble compiling bluez-hcidump-1.18
Date: Wed, 23 Mar 2005 23:46:50 +0100	[thread overview]
Message-ID: <1111618010.1916.19.camel@pegasus> (raw)
In-Reply-To: <423021C200007A66@resmta01.ono.com>

Hi,

> Untar, ./configure and then make and I get this:
> 
> make  all-recursive
> make[1]: Entering directory `/root/bluez-hcidump-1.18'
> Making all in parser
> make[2]: Entering directory `/root/bluez-hcidump-1.18/parser'
> gcc -DHAVE_CONFIG_H -I. -I. -I..     -Wall -O2 -c `test -f 'parser.c' ||
> echo './'`parser.c
> gcc -DHAVE_CONFIG_H -I. -I. -I..     -Wall -O2 -c `test -f 'hci.c' || echo
> './'`hci.c
> hci.c: In function `command_dump':
> hci.c:707: error: `OCF_CHANGE_CONN_LINK_KEY' undeclared (first use in this
> function)
> hci.c:707: error: (Each undeclared identifier is reported only once
> hci.c:707: error: for each function it appears in.)
> hci.c: In function `cmd_complete_dump':
> hci.c:966: error: `OCF_SET_AFH_CLASSIFICATION' undeclared (first use in this
> function)
> hci.c:998: error: `OCF_READ_LINK_QUALITY' undeclared (first use in this function)
> hci.c:1001: error: `OCF_READ_CLOCK' undeclared (first use in this function)
> hci.c: In function `event_dump':
> hci.c:1376: error: `EVT_CHANGE_CONN_LINK_KEY_COMPLETE' undeclared (first
> use in this function)
> hci.c: In function `hci_dump':
> hci.c:1505: error: `HCI_VENDOR_PKT' undeclared (first use in this function)
> make[2]: *** [hci.o] Error 1
> make[2]: Leaving directory `/root/bluez-hcidump-1.18/parser'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/root/bluez-hcidump-1.18'
> make: *** [all] Error 2
> 
> I have no idea where the problem is... Any suggestions?

make sure that bluez-libs-2.15 is installed. This is clearly stated in
the ChangeLog file as an requirement.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-03-23 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 22:38 [Bluez-devel] Trouble compiling bluez-hcidump-1.18 kwyjibo
2005-03-23 22:46 ` Marcel Holtmann [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=1111618010.1916.19.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