From: "Valmantas Palikša" <walmis@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez-4.49 does not build for me.
Date: Mon, 24 Aug 2009 17:27:08 +0300 [thread overview]
Message-ID: <1251124029.19970.1.camel@walmis-desktop> (raw)
In-Reply-To: <2d5a2c100908240652l179a6ad3mc6195db710ae069a@mail.gmail.com>
Here's my errors:
make[1]: *** No rule to make target `tools/bccmd.8', needed by `all-am'.
Stop.
make: *** [all] Error 2
same with hid2hci.
On Mon, 2009-08-24 at 10:52 -0300, Luiz Augusto von Dentz wrote:
> Hi,
>
> On Mon, Aug 24, 2009 at 10:15 AM, Stefan
> Seyfried<stefan.seyfried@googlemail.com> wrote:
> > In file included from lib/sdp.c:50:
> > lib/sdp_lib.h:31:33: error: bluetooth/bluetooth.h: No such file or directory
> > lib/sdp_lib.h:32:27: error: bluetooth/hci.h: No such file or directory
> > make[1]: *** [lib/sdp.lo] Error 1
> > make: *** [all] Error 2
> >
>
> Strange I just compiled it using ./boostrap-configure but I did have
> it installed so
> it is maybe the case where include/ were not being include when
> compiling lib, so
> it only works when one already have those files installed.
>
> > [...]
> > rm -rf src/.libs src/_libs
> > rm -rf test/.libs test/_libs
> > rm -rf tools/.libs tools/_libs
> > gcc -Wall -O2 -D_FORTIFY_SOURCE=2 -fPIC -pie lib/bluetooth.c -o lib/bluetooth
> > /usr/lib64/gcc/x86_64-suse-linux/4.4/../../../../lib64/Scrt1.o: In function `_start':
> > /usr/src/packages/BUILD/glibc-2.10.1/csu/../sysdeps/x86_64/elf/start.S:99: undefined reference to `main'
> > collect2: ld returned 1 exit status
> > make: *** [lib/bluetooth] Error 1
>
> No idea!
>
next prev parent reply other threads:[~2009-08-24 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 13:15 bluez-4.49 does not build for me Stefan Seyfried
2009-08-24 13:52 ` Luiz Augusto von Dentz
2009-08-24 14:27 ` Valmantas Palikša [this message]
2009-08-24 20:06 ` Marcel Holtmann
2009-08-24 14:44 ` Stefan Seyfried
2009-08-24 14:50 ` Luiz Augusto von Dentz
2009-08-24 14:42 ` Stefan Seyfried
2009-08-24 20:05 ` 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=1251124029.19970.1.camel@walmis-desktop \
--to=walmis@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.