public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: Re: bluez-4.49 does not build for me.
Date: Mon, 24 Aug 2009 13:05:22 -0700	[thread overview]
Message-ID: <1251144322.2950.64.camel@localhost.localdomain> (raw)
In-Reply-To: <20090824151514.6eb4f1f6@stoetzler>

Hi Stefan,

> 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

this got fixed now.

> a following "make clean" or "make distclean" is also interesting:
> 
> [...]
> 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

Have seen that once and the never again.

Regards

Marcel



      parent reply	other threads:[~2009-08-24 20:05 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
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 [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=1251144322.2950.64.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stefan.seyfried@googlemail.com \
    /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