From: Sumeet VERMA <sumeet.verma@st.com>
To: "'BlueZ users'" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Audio gaps with bcm2035 and Hama receiver
Date: Tue, 30 Oct 2007 11:55:56 +0530 [thread overview]
Message-ID: <00c201c81abd$bb7b24d0$832fc70a@dlh.st.com> (raw)
In-Reply-To: <472213B6.50402@hccnet.nl>
Hi Remy
I am also facing the same compilation problem. I saw in the mailing list you
were able to resolve it. How did you do it?
Thanks,
Sumeet
-----Original Message-----
From: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Remy Bosch
Sent: Friday, October 26, 2007 9:50 PM
To: BlueZ users
Subject: Re: [Bluez-users] Audio gaps with bcm2035 and Hama receiver
For some reason "rtp.h" can't be found (included in audio/pcm_bluetooth.c).
This blocks my attempt to build it on gentoo without the use of eglib.
The build goes as follows. In the source directory:
The rm -r eglib/{*.c,*.h} # make sure eglib is ignored
autoreconf -fis # Reconfigure
./configure --enable-inotify --enable-hal --enable-usb --enable-alsa
--enable-glib --disable-obex --enable-network --enable-serial --enable-input
--enable-audio --enable-sync --enable-hcid --enable-configfiles
--disable-initscripts --disable-pcmciarules --enable-bccmd --enable-avctrl
--enable-hid2hci --enable-dfutool --localstatedir=/var
make # And then make
This creates the error:
gcc -DHAVE_CONFIG_H -I. -I.. -I../common -I/usr/include/alsa -I../sbc -Wall
-O2 -D_FORTIFY_SOURCE=2 -MT
libasound_module_pcm_bluetooth_la-pcm_bluetooth.lo -MD -MP -MF
.deps/libasound_module_pcm_bluetooth_la-pcm_bluetooth.Tpo -c pcm_bluetooth.c
-fPIC -DPIC -o .libs/libasound_module_pcm_bluetooth_la-pcm_bluetooth.o
pcm_bluetooth.c:41:17: error: rtp.h: No such file or directory
pcm_bluetooth.c: In function 'avdtp_write':
pcm_bluetooth.c:601: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: warning: left-hand operand of comma expression has no
effect
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:603: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:605: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:606: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:607: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:608: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:609: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:610: error: dereferencing pointer to incomplete type
pcm_bluetooth.c:617: error: invalid application of 'sizeof' to incomplete
type 'struct rtp_header'
pcm_bluetooth.c:617: error: invalid application of 'sizeof' to incomplete
type 'struct rtp_payload'
pcm_bluetooth.c: In function 'bluetooth_a2dp_init':
pcm_bluetooth.c:968: error: invalid application of 'sizeof' to incomplete
type 'struct rtp_header'
pcm_bluetooth.c:968: error: invalid application of 'sizeof' to incomplete
type 'struct rtp_payload'
make[2]: *** [libasound_module_pcm_bluetooth_la-pcm_bluetooth.lo] Error 1
make[2]: Leaving directory `/root/bluez-utils-3.21/audio'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/root/bluez-utils-3.21'
make: *** [all] Error 2
Any idea how to fix it?
Thanks!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-10-30 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 16:46 [Bluez-users] Audio gaps with bcm2035 and Hama receiver Remy Bosch
2007-10-25 22:48 ` Marcel Holtmann
2007-10-26 12:53 ` Remy Bosch
2007-10-26 16:20 ` Remy Bosch
2007-10-26 17:35 ` Brad Midgley
2007-10-26 20:26 ` Remy Bosch
2007-10-26 21:46 ` Brad Midgley
2007-10-26 23:40 ` Remy Bosch
2007-10-30 11:29 ` Brad Midgley
2007-10-30 11:49 ` Remy Bosch
2007-10-30 6:25 ` Sumeet VERMA [this message]
2007-10-30 10:22 ` Remy Bosch
2007-10-30 10:23 ` Sumeet VERMA
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='00c201c81abd$bb7b24d0$832fc70a@dlh.st.com' \
--to=sumeet.verma@st.com \
--cc=bluez-users@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