From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] compiling btsco (a2play.o)
Date: Mon, 10 Oct 2005 14:12:13 -0600 [thread overview]
Message-ID: <434ACB1D.8010103@xmission.com> (raw)
In-Reply-To: <200510102149.11567.michael.renner@gmx.de>
Michael,
I think I added the pthreads requirement in the code without specifying
it properly in the autoconf stuff. Strangely, it works on my laptop as-is.
Try updating & configuring it again in a few minutes (I committed a fix)
Brad
Michael Renner wrote:
> Moin,
>
> I just tried to compile the CVS version from yesterday. My machine is a debian
> stable installation (gcc 3.3.5) running a self compiled vanilla 2.6.13 kernel
> with its sources in /usr/src/linux.
>
> As far as I see, every necessary package is installed in a current version.
>
> Running configure gives one error:
> ./configure: line 4182: XIPH_PATH_AO: command not found
>
> Trying to compile the package ends with an error:
> make[2]: Entering directory `/usr/src/btsco'
> gcc -Wall -O2 -o a2play a2play.o -lbluetooth -lbluetooth sbc/libsbc.a
> -lbluetooth
> a2play.o(.text+0x189b): In function `main':
> : undefined reference to `pthread_create'
> a2play.o(.text+0x19e8): In function `main':
> : undefined reference to `pthread_join'
> collect2: ld returned 1 exit status
>
> Whats wrong?
>
> Thanks
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-10-10 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 19:49 [Bluez-devel] compiling btsco (a2play.o) Michael Renner
2005-10-10 20:12 ` Brad Midgley [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=434ACB1D.8010103@xmission.com \
--to=bmidgley@xmission.com \
--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;
as well as URLs for NNTP newsgroup(s).