public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: tam99@t-online.de (Stefan)
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluez-utils compile error
Date: Thu, 12 Aug 2004 15:19:43 +0200	[thread overview]
Message-ID: <200408121519.43356.tam99@t-online.de> (raw)
In-Reply-To: <1092313255.28711.120.camel@pegasus>

Thanks a lot!!
Now it works!
Is this a bug or why I had to remove this lines?

MfG Stefan




On Thursday 12 August 2004 14:20, you wrote:
> 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

  reply	other threads:[~2004-08-12 13:19 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
2004-08-12 13:19   ` Stefan [this message]
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=200408121519.43356.tam99@t-online.de \
    --to=tam99@t-online.de \
    --cc=bluez-users@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