From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan <tam99@t-online.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez-utils compile error
Date: Thu, 12 Aug 2004 14:20:56 +0200 [thread overview]
Message-ID: <1092313255.28711.120.camel@pegasus> (raw)
In-Reply-To: <200408121348.18203.tam99@t-online.de>
Hi Stefan,
> when I try to compile bluez-utils I get the following error:
>
> ...
> c `test -f 'hid2hci.c' || echo './'`hid2hci.c
> gcc -I/usr/include -I/usr/include -Wall -g -O2 -o hid2hci hid2hci.o
> -L/usr/lib -lusb
> /usr/lib/libusb.a(usb.o)(.text+0x7e9): In function `usb_get_busses':
> : multiple definition of `usb_get_busses'
> hid2hci.o(.text+0x0):/home/stefan/bluez-utils-2.9/tools/hid2hci.c:45: first
> defined here
> collect2: ld returned 1 exit status
> make[2]: *** [hid2hci] Error 1
> make[2]: Leaving directory `/home/stefan/bluez-utils-2.9/tools'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/stefan/bluez-utils-2.9'
> make: *** [all] Error 2
> bash-2.05b$
>
> bluez-libs and libusb are installed
remove this:
#ifndef usb_get_busses
struct usb_bus *usb_get_busses(void)
{
return usb_busses;
}
#endif
from the hid2hci.c file and try again.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-08-12 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 11:48 [Bluez-users] bluez-utils compile error Stefan
2004-08-12 12:20 ` Marcel Holtmann [this message]
2004-08-12 13:19 ` Stefan
2004-08-12 13:29 ` Marcel Holtmann
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=1092313255.28711.120.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=tam99@t-online.de \
/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