|
Description
Ruben Jenster
2005-05-05 04:48:57 UTC
Created attachment 58130 [details]
bluetooth-alsa-1.6-r2.ebuild
I would recommmend to put it into net-wireless/bluetooth-alsa.
Created attachment 58131 [details]
bluetooth-alsa-1.6.tar.bz2
This is a snapshot from the bluetooth-alsa cvs (kernel subdir) from 05-05-2005
Created attachment 58132 [details]
btsco-0.4a.ebuild
I would recommend to put it into net-wireless/btsco.
Created attachment 58133 [details]
btsco-0.4a.tar.bz2
This is a snapshot from the bluetooth-alsa cvs from 05-05-2005.
Sound team: any takers? *** Bug 81036 has been marked as a duplicate of this bug. *** would be cool to have this in ASAP! But I'm neither a sound nor a bluetooth geek, though I have both up and running. ;-) since i take bluetooth stuff, i'll put this on my queue as i do have a bluetooth headset i can test it with. I am willing to pitch in. I have started using gentoo but don't have much experience with ebuilds. I do have bluetooth headset and willing to contribute to it in my free time. I am tring now to figure out how to use this ebuild. Got some expirince with BT. Will edit this as soon as it works. (In reply to comment #10) > I am tring now to figure out how to use this ebuild. > Got some expirince with BT. > Will edit this as soon as it works. > managed to setup overlay.can't ebuild bluetooth-alsa digest. "couldn't connect to 132.194.22.137 port 33172: Connection timed out Retrying." and so on hope it will do better tomorrow Created attachment 74911 [details]
bluetooth-alsa cvs ebuild
Created attachment 74912 [details]
btsco cvs ebuild
(In reply to comment #13) > Created an attachment (id=74912) [edit] > btsco cvs ebuild > *** [Gentoo] sanity check failed! *** *** libtool.m4 and ltmain.sh have a version mismatch! *** *** (libtool.m4 = 1.5.20, ltmain.sh = 1.5.6) *** Please run: libtoolize --copy --force if appropriate, please contact the maintainer of this package (or your distribution) for help. make: *** No targets specified and no makefile found. Stop. Created attachment 75892 [details]
btsco-cvs-0.4-r1.ebuild
using 'libtoolize --copy --force' should work now.
Happy new year.
Regards,
Ruben.
Created attachment 75989 [details]
headset initscript
This is a sample initscript that can be used to establish a headset connection.
Just save it under /etc/init.d/headset. Furthermore you have to put your headset address ( e. g. BDADDR="xx:xx:xx:xx:xx:xx") into /etc/conf.d/headset.
in src_install function of btsco-cvs-0.4-r1.ebuild you have /sbc/sbcinfo. This produces as error when emerging for the first time: /usr/local/portage/net-wireless/btsco-cvs/btsco-cvs-0.4-r1.ebuild: line 37: /sbc/sbcinfo: No such file or directory I'm not sure why you are trying to run that program at install time, cause all it gives me if I run it without arguments is it's usage: Usage: sbcinfo <file> Should this file be installed by this package? Created attachment 76076 [details]
btsco-cvs-0.4-r1.ebuild
Thanks. I've experimented the ebuild and missed to clean it up.
removed '/sbc/sbcinfo'
Guys, the bluetooth-alsa ebuild is totally broken... There are a few eclasses that _are_ to be used when installing modules. KBUILD_OUTPUT is not handled This is an _INTERACTIVE_ ebuild (Proceed with enter...) - No way! Isn't a cvs ebuild supposed to checkout a certain version? Or a date at least? This will always get HEAD, which most probably is unstable. Let me have a look at it. Created attachment 76128 [details] net-wireless/bluetooth-alsa-cvs-1.6-r2.ebuild net-wireless/bluetooth-alsa-cvs-1.6-r2.ebuild This obsoletes the attachment #58130 [details], please mark as such. It is a complete rewrite, using linux-mod and linux-info properly. Created attachment 76129 [details] net-wireless/btsco-cvs-0.4-r1.ebuild net-wireless/btsco-cvs-0.4-r1.ebuild This obsoletes attachment #76076 [details] ,please mark as such. It is a complete rewrite, using linux-info properly. This one is unified with attachment #76128 [details] My full overlay is available at: rsync://rsync.tar.bz/gentoo-portage-pkalin (or fetch rsync://rsync.tar.bz/gentoo-portage-pkalin/pkalin.syncsource ) Now, I feel that these two ebuilds can get the beating and made it to portage soon. TODO: make ebuild for A2DP or combine it with one of the above add the init scripts Created attachment 76130 [details]
net-wireless/bluetooth-alsa-kernel-0.2_alpha20060104.ebuild
After a lot of thinking and hunting around, I came to the conclusion that these names (bluetooth-alsa-{kernel,utils}) will be easy to remember and understand.
The project itself is not very active and has not decided on a name yet (RTFM).
No releases yet, so these are the current HEAD of CVS (How can I checkout a specific revision with cvs.eclass? ) If it only was SVN, not cvs...
The version is a bit vague, but according to the Ebuild HOWTO there is no better naming as of yet. (0.2 was the only version I could find by `grep -R -i version` in the sources of bluetooth-alsa-utils, the -kernel has no verion mentioned, but comes from the same source, so same version).
So here comes net-wireless/bluetooth-alsa-kernel-0.2_alpha20060104.ebuild to be followed by the utils.
Created attachment 76131 [details]
net-wireless/bluetooth-alsa-utils-0.2_alpha20060104.ebuild
The utils package is here.
As usual, the full overlay is at rsync://rsync.tar.bz/gentoo-portage-pkalin
If the reporter or a dev can change the summary and obsolete the previous ebuilds, that may get a bit more testing quicker.
I think the attached file bluetooth-alsa-1.6-r2.ebuild should be named : net-wireless/bluetooth-alsa-cvs-1.6-r2.ebuild I think the attached file bluetooth-alsa-1.6-r2.ebuild should be named : net-wireless/bluetooth-alsa-cvs-1.6-r2.ebuild and also bluetooth-alsa-1.6.tar.bz2 -> dist/bluetooth-alsa-cvs-1.6-r2.tar.bz2 You need to use only the latest (the two _alpha20060104 ebuilds). On a (new) system: kpc ~ # emerge -at bluetooth-alsa-utils These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [ebuild N ] net-wireless/bluetooth-alsa-utils-0.2_alpha20060104 0 kB [1] [ebuild N ] net-wireless/bluetooth-alsa-kernel-0.2_alpha20060104 0 kB [1] Total size of downloads: 0 kB Portage overlays: [1] /usr/local/portage/pkalin Do you want me to merge these packages? [Yes/No] Y ... However at the moment, SourceForge CVS for bluetooth-alsa is down... http://cvs.sourceforge.net/viewcvs.py/bluetooth-alsa Somebody, please mark the other ebuilds as deprecated for people not to be mistaken. I just published this in gentoo wiki: http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset hope to get my headset back working. I am using net-wireless/bluetooth-alsa-utils-0.2_alpha20060104 Today I read that some thing concering oss emulation in alsa was fixed in the recent release.So I followed the gentoo alsa guide and switched to use alsa-driver. If I try to emerge the ebuild I get: SND_HWDEP is not set! Plese select a config like SND_USB_AUDIO or SND_EMU10K1; see under Drivers|Sound|ALSA, see inside PCI or US B I use usb-audio fine via the alsa-driver. ovcurse it doent appear in the kernel .config How can we fix it? Niv Maybe there should be some way to override the init.d to use btsco instead of btsco2.. btsco2 doesn't work for me.. To comment#28: I am not sure if you can configure SND_USB_AUDIO without it selecting the SND_HWDEP ... Anyway, unless you have SND_HWDEP selected you will not be able to use bluetooth-alsa. What kernel version? gentoo/vanilla/other? See if you have SND_HWDEP enabled, if not enable SND_EMU10k1 and recompile/install kernel. To comment#29: Can't you just edit it in the /etc/init.d script? Try and report (success :-) Created attachment 77427 [details]
Bluetooth alsa working well when using alsa in kernel
see alsa.after.txt
Created attachment 77428 [details]
using alsa-driver bluetooth alsa doesnt work
state after applying alsa-driver. see alsa.before.txt when it worked
I have just attached alsa.before and after. first describes a working status using the given ebuild. the second is when I removed alsa from the kernel and used alsa-driver. I marked out the line concering SND_HWDEP in order to emerge the ebuild. as can be seen I compiled a module for SND_EMU10k1. yet hcidump -X -V gives noting. like its failing in the alsa level. Niv Created attachment 79189 [details]
net-wireless/bluetooth-alsa-kernel/bluetooth-alsa-kernel-0.41.ebuild
Since SF Anonymous CVS sucks, they have a btsco-0.41 package and I modified Kalin's to use this instead of CVS.
Created attachment 79190 [details]
net-wireless/bluetooth-alsa-utils/bluetooth-alsa-utils-0.41.ebuild
Since SF Anonymous CVS sucks, they have a btsco-0.41 package and I modified
Kalin's to use this instead of CVS.
Followed http://www.gentoo.org/doc/en/bluetooth-guide.xml until I could successfully ping my headset (yes!). Then continued with: http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset. Set up portage overlay in /usr/local/portage as laid out in http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds. Downloaded ebuilds and digested as follows: ebuild /usr/local/portage/net-wireless/bluetooth-alsa-kernel/ bluetooth-alsa-kernel-0.41.ebuild digest ebuild /usr/local/portage/net-wireless/bluetooth-alsa-utils/ bluetooth-alsa-utils-0.41.ebuild digest Then added to them /etc/portage/package.keywords Then the emerge failed, it seems to be looking for a missing "build" directory and I don't know why: emerge -at bluetooth-alsa-kernel These are the packages that I would merge, in reverse order: Calculating dependencies ...done! [ebuild N ] net-wireless/bluetooth-alsa-kernel-0.41 Do you want me to merge these packages? [Yes/No] yes >>> emerge (1 of 1) net-wireless/bluetooth-alsa-kernel-0.41 to / >>> md5 files ;-) bluetooth-alsa-kernel-0.41.ebuild >>> md5 files ;-) files/digest-bluetooth-alsa-kernel-0.41 >>> md5 src_uri ;-) btsco-0.41.tar.gz * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.14-gentoo-r5 * Checking for suitable kernel configuration options: >>> Unpacking source... >>> Unpacking btsco-0.41.tar.gz to /var/tmp/portage/bluetooth-alsa-kernel-0.41/work >>> Source unpacked. * Preparing snd-bt-sco module make: *** /lib/modules/2.6.14-gentoo-r5/build: No such file or directory. Stop. make: *** [default] Error 2 !!! ERROR: net-wireless/bluetooth-alsa-kernel-0.41 failed. !!! Function linux-mod_src_compile, Line 505, Exitcode 2 !!! Unable to make -j1 default. !!! If you need support, post the topmost build error, NOT this status message. Am willing to supply more information if necessary. Created attachment 79835 [details]
net-wireless/bluetooth-alsa-0.41.ebuild
Give a try to this one.
Created attachment 79836 [details]
net-wireless/bluetooth-alsa-9999.ebuild
Give a try to this one. (CVS)
Now managed to emerge alsa-9999.ebuild without errors. The problem was the following: till now I had never issued "make modules_install". Thus the symlink build -> /usr/src/linux-2.6.14-gentoo-r5 in directory /lib/modules/2.6.14-gentoo-r5/ was never created. (This was because I so far compiled everything into the kernel, although I have emerged one kernel module through emerge which must have been build since it's working?) After running make modules_install (even when there is not a single module to make or install) the alsa-9999.ebuild emerges without errors. I don't know enough about ebuilds to say whether this can be considered a bug in the ebuild or even in portage or gentoo, but in the latter case I guess it would have been filed already. After finding out and fixing the symlink I first tried to emerge the original alsa-0.41.ebuild, but then portage gave me a kind security error because somehow the cvs-ebuild seemed to be conflicting with the 0.41. I don't understand enough about portage to diagnose this problem, so I proceeded with emerging the cvs. I'm pretty sure the 0.41 version would have worked as well, though, since the original error message of the 0.41 (about the build directory, see previous post) was exactly the same as the cvs one. Thanks Octovio, for providing the alternative. I will now proceed to check if I can get my headset to work with some applications e.g. skype (I enabled the skype use flag for the emerge). Bram To comment #37: Octavio, whould you give us a good reason why you didn't like the proposed ebuilds in comment #34 and comment #35 by Gustavo? If you cannot, please mark obsolete. To comment #38: I don't find it necessary to provide a CVS ebuild now that the project has released version 0.41 (My first proposals use CVS because then there were no realeses available at all). Plese consider marking obsolete. And putting things like version 9999 and a new category (bluetooth-alsa) is out of the question IMHO. I have updated my overlay (see comment #22) with the 0.41 versions from Gustavo and they look good enough to me for inclusion. Alastair, as a bug asignee, don't you feel it is time to put in the tree to get some more testing? Can't compile bluetooth-alsa/bluetooth-alsa-9999.ebuild on ~amd64 with alsa (--enable-alsaplugin) -------------------------------------------------------------------------------- ** Warning: Linking the shared library libasound_module_pcm_a2dp.la against the *** static library ../sbc/libsbc.a is not portable! x86_64-pc-linux-gnu-gcc -shared .libs/pcm_a2dp.o -L/usr/lib64 ../sbc/libsbc.a /usr/lib64/libasound.so -lm -ldl -lpthread /usr/lib64/libbluetooth.so -march=k8 -Wl,-soname -Wl,libasound_module_pcm_a2dp.so -o .libs/libasound_module_pcm_a2dp.so /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: ../sbc/libsbc.a(sbc.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../sbc/libsbc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [libasound_module_pcm_a2dp.la] Error 1 make[2]: Leaving directory `/var/tmp/portage/bluetooth-alsa-9999/work/btsco/alsa-plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/bluetooth-alsa-9999/work/btsco' make: *** [all] Error 2 !!! ERROR: net-wireless/bluetooth-alsa-9999 failed. Call stack: ebuild.sh, line 1894: Called dyn_compile ebuild.sh, line 941: Called src_compile !!! emake failed !!! If you need support, post the topmost build error, and the call stack if relevant. ----------------------------------------------------------------------------- jey btsco # emerge info Portage 2.1_pre4-r1 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.6-r2, 2.6.15-archck4 x86_64) ================================================================= ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-march=k8 -O2 -pipe" I think the code is a little broken jey (In reply to comment #40) > Octavio, whould you give us a good reason why you didn't like the proposed > ebuilds Please see yourself the diferences between both. > And putting things like version 9999 and It's just for testing the CVS branch, it doesn't hurts you and is not supposed to be inside the tree. > new category (bluetooth-alsa) is out of the question IMHO. bluetooth-alsa is the name of the package, not a category. x-D. You should focus in the QA of the ebuild and not in trivial things like names. The maintainer would change that without problems. > I have updated my overlay (see comment #22) with the 0.41 versions > from Gustavo and they look good enough to me for inclusion. They doesn't look good enough for inclusion, even my ebuild have problems like proper use of linux-mod (Making sure the ebuild is compiled from KV_DIR and not from `uname -r), Gustavo's one doesn't inherit autotools eclass, don't have proper RDPEND atoms, et al. (In reply to comment #42) > (In reply to comment #40) > > Octavio, whould you give us a good reason why you didn't like the proposed > > ebuilds > > Please see yourself the diferences between both. OK, I tired now. I din't try before as they were too different to compare. > > I have updated my overlay (see comment #22) with the 0.41 versions > > from Gustavo and they look good enough to me for inclusion. > > They doesn't look good enough for inclusion, even my ebuild have problems like Now we are talking! Thank you for the points below: > proper use of linux-mod (Making sure the ebuild is compiled from KV_DIR and not from `uname -r), ... where did you see `uname -r`? Is it the definition of ${S} to be one level up from mine/Gustavo's ebuilds? Please give me more info, as I am not an expert of linux_mod > Gustavo's one doesn't inherit autotools eclass, don't have > proper RDPEND atoms, et al. Pint taken, ebuilds fixed. Will attach them in a few minutes, available from my overlay (see comment#21 for URI) I still think that we should have 2 separate ebuilds (kernel+utils) to mirror other packages behavior in the tree. Thanks for changing the name of your attachmets, that makes it clearer. Created attachment 80065 [details] net-wireless/bluetooth-alsa-kernel-0.41.ebuild (further cleanup) Improvments per comment#42 and other fixups: Proper dependencies to >=virtual/linux-sources-2.6 then, no need to check if it is a 2.6 kernel Improve wording in ERROR_* add BUILD_TARGETS (needed?) Created attachment 80066 [details] net-wireless/bluetooth-alsa-utils-0.41.ebuild (further cleanup) Improvments per comment#42 and other fixups: inherit autotools add IUSE="alsa ao skype" fix DEPEND and RDEPEND no need for pkg_setup() we RDEPEND on bluetooth-alsa-kernel fix src_compile(), src_install() to use autotools and new useflags Kalin pls rsync to rsync.tar.bz :-) Sweet, emerged fine here. none of that * SND_HWDEP is not set! Plese select a config like SND_USB_AUDIO or SND_EMU10K1; see under Drivers|Sound|ALSA, see inside PCI or USB I used to see. (In reply to comment #46) > Kalin pls rsync to rsync.tar.bz :-) I don't understand what you mean :-| Or was it a joke? Just to make life easier, I made my overlay available through http as well: http://rsync.tar.bz/ > Sweet, > emerged fine here. none of that > * SND_HWDEP is not set! Plese select a > config like SND_USB_AUDIO or SND_EMU10K1; see under > Drivers|Sound|ALSA, see inside PCI or USB Hmm, does it print this with tabs inside the text?? Last time it was fine, but will retest later. Oops, I need to change the type of my attachments as well... I was just asking that you update site that you offer your ebuilds. I tried rsunc to it, and didnt get the new ebuilds. I emerge the new 0.41 kernel and utils. worked like a charm. I have a usb audio sound card so the dependency SND_HWDEP is met and I dont need to add the emu10k1 sound card. Previos ebuilds , didnt find that in my system I am using the alsa-driver , not the alsa in the kernel, so I guess that was the reason . Well now that both emerged well I am missing the snd-bt-sco.ko file. where is it? Niv (In reply to comment #48) > I was just asking that you update site that you offer your ebuilds. I tried > rsunc to it, and didnt get the new ebuilds. That is strange, I checked the rsync setup and everything seems OK. > I am using the alsa-driver, not the alsa in the kernel, so I guess that was > the reason . Any reason for that? > Well now that both emerged well I am missing the snd-bt-sco.ko file. where is > it? What does this command give you? cat /var/db/pkg/net-wireless/bluetooth-alsa-kernel-0.41/CONTENTS PORTDIR_OVERLAY="/usr/local/portage/pkalin" USE="skype ao" emerge -av bluetooth-alsa-kernel bluetooth-alsa-utils GIVES-> dir /usr dir /usr/bin obj /usr/bin/btsco f30e7730526287b2907381de1c84b050 1140478908 obj /usr/bin/a2play 7629df86ec5779fc69c26bb3a9deb183 1140478908 obj /usr/bin/a2recv 5ba51694810bee1ae45ac895c4f37e3f 1140478908 obj /usr/bin/avrecv f2c49bf042a716b2ebae4fd44861e3db 1140478908 obj /usr/bin/btsco2 9622b722e29a40fb52da4d05c5e7896f 1140478908 dir /usr/lib dir /usr/lib/alsa-lib obj /usr/lib/alsa-lib/libasound_module_pcm_headset.la c6073d3623c4d1fb5f059c5f12af1e66 1140478908 obj /usr/lib/alsa-lib/libasound_module_pcm_headset.so 7d51dca3cbecddceb98809f7d6819bc0 1140478908 obj /usr/lib/alsa-lib/libasound_module_pcm_a2dp.la 23c1acb7683bc901a4dcd0fac4e7eb57 1140478908 obj /usr/lib/alsa-lib/libasound_module_pcm_a2dp.so 08a87029c6a44a4726af1d0d72d706d3 1140478908 obj /usr/lib/alsa-lib/libasound_module_pcm_a2dp.a 47c36c45a4123d0161a5d3bcfd98bddb 1140478908 obj /usr/lib/alsa-lib/libasound_module_pcm_headset.a cb198f224c9c67e0c9d0bd9af0224831 1140478908 dir /usr/share dir /usr/share/doc dir /usr/share/doc/bluetooth-alsa-kernel-0.41 dir /usr/share/doc/bluetooth-alsa-kernel-0.41/Skype obj /usr/share/doc/bluetooth-alsa-kernel-0.41/Skype/README.gz 14e07aeab7b13a22099b68540c543b6c 1140478908 obj /usr/share/doc/bluetooth-alsa-kernel-0.41/Skype/ChangeLog.gz 9c77a9beecb534314c5e348ea8f99db7 1140478908 obj /usr/share/doc/bluetooth-alsa-kernel-0.41/README.gz d54cef9d4cb751489a58acdb113c5414 1140478908 obj /usr/share/doc/bluetooth-alsa-kernel-0.41/COPYING.LIB.gz 892e831eca92fbf7247679d84cfc4e56 1140478908 obj /usr/share/doc/bluetooth-alsa-kernel-0.41/COPYING.gz fafba84e2e97d40a910fd464323bd279 1140478908 obj /usr/share/doc/bluetooth-alsa-kernel-0.41/README.alsaplugin.gz 0a65ef027426a6e8391939d9a0515cd1 1140478908 dir /usr/libexec dir /usr/libexec/bluetooth-alsa-kernel obj /usr/libexec/bluetooth-alsa-kernel/bin 7f47ac6ac551252af2053519426d6831 1140478908 sym /usr/bin/skype_bt_hijacker -> /usr/libexec/bluetooth-alsa-kernel/skype_bt_hijacker 1140478908 and no snd-bt-sco.ko Created attachment 80337 [details]
.kde/share/apps/kbluetoothd/discovery_jobs/Headset
I'm using this script instead of /etc/init.d/headset.
Just use kbluetoothd and use this script as the discovery action. It will launch btsco -s -f $HWADDR.
(In reply to comment #50) OK, something is wrong. Do you have PORT_LOGDIR defined in /etc/make.conf? If not set it up. Then run: PORTDIR_OVERLAY="/usr/local/portage/pkalin" USE="skype ao" emerge -a bluetooth-alsa-kernel And send post the log of that emerge from "* Determining the location of the kernel source code" to ">>> net-wireless/bluetooth-alsa-kernel-0.41 merged." It should be about 50-60 lines. Created attachment 80338 [details] net-wireless/bluetooth-alsa-kernel-0.41.ebuild (further cleanup 2) Fixing ERROR_HCIUSB_SCO to ERROR_BT_HCIUSB_SCO; word-wrapping was ugly My full overlay is available at: rsync://rsync.tar.bz/gentoo-portage-pkalin http://rsync.tar.bz/ (or use http://rsync.tar.bz/pkalin.syncsource with gensync) Comments on the ebuilds and testers are welcome. why is media-sound/alsa-driver blocking bt-alsa-kernel ? I have a usb sound card and when I emerge it, I get the needed dependency module: /lib/modules/2.6.15-ck3-r1/alsa-driver/acore/snd-hwdep.ko Anyone notice that this always builds against the running kernel source tree, and not the kernel tree linked by /usr/src/linux? I use modules-rebuild to rebuild all packages that provide kernel modules before rebooting into the the new kernel, and without fail, this package builds a module against /lib/modules/`uname -r`/build, while installing the module into /lib/modules/${KV_FULL}. Observe:
emerge -va bluetooth-alsa-kernel
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] net-wireless/bluetooth-alsa-kernel-0.41 0 kB [3]
Total size of downloads: 0 kB
Portage overlays:
[1] /usr/local/portage
[2] /usr/local/xgl
[3] /usr/local/bluetooth_overlay
[4] /usr/local/portage.openbox
Would you like to merge these packages? [Yes/No]
>>> Emerging (1 of 1) net-wireless/bluetooth-alsa-kernel-0.41 to /
>>> checking ebuild checksums
>>> checking auxfile checksums
>>> checking miscfile checksums
>>> checking distfiles checksums
* Determining the location of the kernel source code
* Found kernel source directory:
* /usr/src/linux
* Found sources for kernel version:
* 2.6.16.11
* Checking for suitable kernel configuration options:
>>> Unpacking source...
>>> Unpacking btsco-0.41.tar.gz to /var/tmp/portage/bluetooth-alsa-kernel-0.41/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/bluetooth-alsa-kernel-0.41/work/btsco-0.41/kernel ...
* Preparing snd-bt-sco module
make[1]: Entering directory `/usr/src/linux-2.6.16.9'
CC [M] /var/tmp/portage/bluetooth-alsa-kernel-0.41/work/btsco-0.41/kernel/btsco.o
LD [M] /var/tmp/portage/bluetooth-alsa-kernel-0.41/work/btsco-0.41/kernel/snd-bt-sco.o
Building modules, stage 2.
MODPOST
CC /var/tmp/portage/bluetooth-alsa-kernel-0.41/work/btsco-0.41/kernel/snd-bt-sco.mod.o
LD [M] /var/tmp/portage/bluetooth-alsa-kernel-0.41/work/btsco-0.41/kernel/snd-bt-sco.ko
make[1]: Leaving directory `/usr/src/linux-2.6.16.9'
>>> Source compiled.
>>> Test phase [not enabled]: net-wireless/bluetooth-alsa-kernel-0.41
>>> Install bluetooth-alsa-kernel-0.41 into /var/tmp/portage/bluetooth-alsa-kernel-0.41/image/ category net-wireless
* Installing snd-bt-sco module
>>> Completed installing bluetooth-alsa-kernel-0.41 into /var/tmp/portage/bluetooth-alsa-kernel-0.41/image/
man:
strip: x86_64-pc-linux-gnu-strip --strip-unneeded
>>> Merging net-wireless/bluetooth-alsa-kernel-0.41 to /
--- /lib/
--- /lib/modules/
--- /lib/modules/2.6.16.11/
--- /lib/modules/2.6.16.11/misc/
>>> /lib/modules/2.6.16.11/misc/snd-bt-sco.ko
>>> Safely unmerging already-installed instance...
--- cfgpro obj /lib/modules/2.6.16.11/misc/snd-bt-sco.ko
--- cfgpro dir /lib/modules/2.6.16.11/misc
--- cfgpro dir /lib/modules/2.6.16.11
--- !empty dir /lib/modules
--- !empty dir /lib
* Removing net-wireless/bluetooth-alsa-kernel-0.41 from moduledb.
>>> Original instance of package unmerged safely.
* Updating module dependencies for 2.6.16.11 ... [ ok ]
* Adding module to moduledb.
>>> Regenerating /etc/ld.so.cache...
>>> net-wireless/bluetooth-alsa-kernel-0.41 merged.
>>> No packages selected for removal by clean.
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
A quick look at /var/tmp/portage/bluetooth-alsa-kernel-0.41/work/btsco-0.41/kernel/Makefile shows:
default:
@make -C /lib/modules/`uname -r`/build M=`pwd` modules
install:
@make -C /lib/modules/`uname -r`/build M=`pwd` modules_install
clean:
@make -C /lib/modules/`uname -r`/build M=`pwd` clean
This will not do.
So I created a new ebuild which patches the static Makefile to use /usr/src/linux. I wasn't able to find a linux-mod function to do this, so I just used sed. It works.
Daniel
Created attachment 86024 [details]
net-wireless/bluetooth-alsa-kernel-0.41.ebuild (build against /usr/src/linux)
I also removed one line that read:
BUILD_TARGETS="default"
since this was already defined once.
The diff between the "further cleanup 2" ebuild and mine, for easy reference:
--- bluetooth-alsa-kernel-0.41-old.ebuild 2006-05-02 13:59:50.703411104 -0700
+++ bluetooth-alsa-kernel-0.41.ebuild 2006-05-02 14:09:28.152209680 -0700
@@ -40,7 +40,8 @@
}
src_compile() {
- BUILD_TARGETS="default"
+ einfo "Patching ${S}/Makefile to use '${KV_DIR}'"
+ sed -i ${S}/Makefile -e "s,/lib/modules/\`uname -r\`/build,${KV_DIR},g" || die "Unable to patch Makefile"
MODULE_NAMES="snd-bt-sco()"
BUILD_PARAMS="-j1"
BUILD_TARGETS="default"
(In reply to comment #41) > Can't compile bluetooth-alsa/bluetooth-alsa-9999.ebuild on ~amd64 with alsa > (--enable-alsaplugin) > [...] I also have the same problem with bluetooth-alsa-utils, version 0.41. The output is: ---------------------------------------------------- [blah blah blah] creating libasound_module_pcm_headset.la *** Warning: Linking the shared library libasound_module_pcm_a2dp.la against the *** static library ../sbc/libsbc.a is not portable! (cd .libs && rm -f libasound_module_pcm_headset.la && ln -s ../libasound_module_pcm_headset.la libasound_module_pcm_headset.la) x86_64-pc-linux-gnu-gcc -shared .libs/pcm_a2dp.o -L/usr/lib64 ../sbc/libsbc.a /usr/lib64/libasound.so -lm -ldl -lpthread /usr/lib64/libbluetooth.so -march=athlon64 -Wl,-soname -Wl,libasound_module_pcm_a2dp.so -o .libs/libasound_module_pcm_a2dp.so /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: ../sbc/libsbc.a(sbc.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../sbc/libsbc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [libasound_module_pcm_a2dp.la] Error 1 make[2]: Leaving directory `/var/tmp/portage/bluetooth-alsa-utils-0.41/work/btsco-0.41/alsa-plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/bluetooth-alsa-utils-0.41/work/btsco-0.41' make: *** [all] Error 2 !!! ERROR: net-wireless/bluetooth-alsa-utils-0.41 failed. !!! Function src_compile, Line 40, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message. ---------------------------------------------------- I fear this might be something unrelated to the ebuild, maybe move upstream? Can anyone of the more knowledgeable in this page enlighen us? Or is there a quick fix? (In reply to comment #58) > I also have the same problem with bluetooth-alsa-utils, version 0.41. Apparently, the problem on AMD64 is caused by the lines: ------------ $(use_enable alsa alsaplugin) \ $(use_enable ao ) || die "econf failed" ------------ Commenting them out makes the ebuild compile fine. Whether it works correctly, I am not sure since I am neither sure what these lines do exactly. Anyway, my two cents. i will try and test this over the next couple of days, but the kernel ebuild is looking good. at the moment the bluetooth-alsa.sf.net isn't responding, so i'll have to check back later. i like that you've split the kernel and the userspace utilities into two different ebuilds, but i'm not sure about renaming the project to bluetooth-alsa rather than btsco. i'm worried it might be confusing if people were to look for btsco and not find it using 'emerge search'. Hi, I used the latest version of these ebuilds on a x86 system without any problem. My Logitech headset is working perfectly and I can use it with Ekiga :) Thank you I've cleaned up the ebuilds a little and put them in my development overlay in http://overlays.gentoo.org/svn/dev/liquidx/net-wireless/ as btsco and btsco-kernel. Most of the changes are just with the DEPENDs and reducing the amount of redundant code in btsco-kernel. Please take a look at it and test it. My bluetooth headset has broken so I'm unable to test it. But I'll commit them to the portage tree if I get verification that this is all working. Could you add your overlay to the list used by layman? (In reply to comment #62) > Please take a look at it and test it. > I'll test it this evening. However, the headset initscript should be part of btsco. Or is it possible to connect to the headset without root permissions? I didn't try this. Thank you I've added my overlay to layman under the name 'liquidx', also fixed a minor problem with src_unpack Created attachment 92013 [details]
headset init script with choice over BTSCO/BTSCO2
This updated headset scripts allows to configure in /etc/conf.d/headset whether you use btsco or btsco2 by setting BTSCO variable to one of these values. If you don't define BTSCO then it currently defaults to btsco.
The new ebuilds are working fine here. I tried the new headset script, and it seems to work well with btsco, but btsco2 doesn't send audio to my headset. I confess I have no idea what the difference is between btsco and btsco2, but as long as one of them works, I'm happy. Daniel Work fine here too :) I'm able to use btsco and btsco2 without root privilegies. Thus, I prefer not using an initscript for that. (In reply to comment #67, #68) > The new ebuilds are working fine here. I tried the new headset script, and it > seems to work well with btsco, but btsco2 doesn't send audio to my headset. This precisely why I have modified the script. Btsco2 does not work for me, either. However as I can see in comment #68 it may be more suitable not to use an init script at all. I have a lot of understanding for that. It is easier to write a wrapper script for skype, etc to connect the headset this way, than when using an init script. Still I would be most happy if connecting headsets would happen in the same manner as with bluetooth mouse. One should pair the device once for all. After pairing just turning the headset on should connect it and create an alsa device. This is precisely what happens with mice (I guess hidd is doing that). I do not know the infrustructure well enough to propose how to achieve this with headsets though. Hi there, the ebuild in layman::liquidx has the same problem described in comment #41. As described under http://devmanual.gentoo.org/archs/amd64/index.html you have to build shared libs (and so static libs you want to link into shared libs like the libsbc.a which produces the error) with -fPIC. Actually I don't know how to do that with autotools :( A simple hack did it for me, but it was so ugly, I won't post it here ;) Using the btsco and btsco-kernel packages from the liquidx overlay I get a segmentation fault when trying anything with a2play (and my Jabra BT620s), like this: mpg123 --au - /Data/Music/Library/Songs/Abel/De\ stilte\ voorbij/Abel\ -\ Onderweg.mp3 | a2play 00:13:17:70:49:52 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59s-r11 (2000/Oct/27). Written and copyrights by Michael Hipp. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Onderweg Artist: Abel Album : De stilte voorbij Year : 2000 Comment: Genre : Unknown Directory: /Data/Music/Library/Songs/Abel/De stilte voorbij/ Playing MPEG stream from Abel - Onderweg.mp3 ... Found new ID3 Header MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo subbands = 8 blocks = 16 bitpool = 32 len=2048 Header size=32 Sample Rate:44100 Channels:2 Segmentatie fout Doing a make myself with code from the bluetooth-alsa cvs however makes it work. Still, the quality with a2dp isn't perfect (some chirping). I hope this gets improved soon. With btsco it's even worse and mono. btsco2 doesn't work (can anyone explain the btsco-btsco2 difference plz?). so we should make a snapshot of the current cvs then rather than the the release. I have "fixed" btsco-0.41 ebuild to make it compile on amd64.
I'm not quite sure what the other consequences are, but I managed to get my headset working with no apperant side effects.
What needed to be changed was the src_compile() method:
--- before ---
src_compile() {
local myconf
export WANT_AUTOMAKE="1.9.6"
eautoreconf || die "autotools failed"
shared = [ !amd64 && alsa ]
econf \
$(use_enable alsa alsaplugin) \
$(use_enable ao ) || die "econf failed"
emake || die "emake failed"
if use skype; then
cd ${MY_S_SKYPE}
emake || die "emake failed"
fi
}
--- after ---
src_compile() {
local myconf
local shared
export WANT_AUTOMAKE="1.9.6"
eautoreconf || die "autotools failed"
shared = [ !amd64 && alsa ]
econf \
$(use_enable alsa alsaplugin) \
$(use_enable shared) \
$(use_with amd64 pic) \
$(use_enable ao ) || die "econf failed"
emake || die "emake failed"
if use skype; then
cd ${MY_S_SKYPE}
emake || die "emake failed"
fi
}
hope this helps anyone and someone makes a real ebuild.
I mean no offence but how is the status of this ebuild? Last ebuild is from may and last comment was over two months ago. I would love to see it in portage. Alastair seems to be missing again, and I'm alone handling ALSA at the moment. Considering I don't have a bluetooth device to work with, I cannot handle this bug myself. So unless someone is going to send me a pair of bluetooth headphones, I doubt I would be able to do anything about this. It's really a bit messy here. Using eix, I found that bluetooth-alsa is in layman/erazor, layman/break-my-gentoo-main; btsco-kernel is in layman/sabayon. In the same time btsco should be replaced with plugz/A2DP and it's not in any overlay yet. Any volunteer to create new cvs ebuild for plugz and put everything in one place?.. Thanks. Created attachment 105443 [details]
btsco-0.5.ebuild
Created attachment 105450 [details]
btsco init script (easier connection/disconnection of headset)
Created attachment 105556 [details]
btsco init script UPDATED (easier connection/disconnection of headset)
Comment on attachment 105443 [details]
btsco-0.5.ebuild
Since version 0.5 bluetooth-alsa-kernel & bluetooth-alsa-utils is no more needed) Also corrected the name to just btsco
Created attachment 105793 [details] bluetooth-alsa-kernel-0.5.ebuild Please bear with me, cannot post more that one file at a time. My overlay is available anonymously (RO) by rsync [1], HTTP [2] and SVN/HTTPS [3] so use what you prefer. [1] rsync://rsync.tar.bz/gentoo-portage-pkalin [2] http://rsync.tar.bz/ [3] https://svn.tar.bz/repos/pkalin/trunk Created attachment 105795 [details]
bluetooth-alsa-utils-0.5.ebuild
2/3 Please bear with me, cannot post more that one file at a time.
3/3 Please bear with me, hope this is last. If you use subversion client you can see the logs ( `svn log https://svn.tar.bz/repos/pkalin/net-wireless/ -r 60:HEAD -v`), but for those who cannot or are lazy here it is (from -r143): `svn merge -r 135:142 https://svn.tar.bz/repos/pkalin/branches/damn_bluetooth-alsa/ pkalin/` Only USE=-alsa is working (i.e. a2dp is not comiled) until someone makes ebuilds for libsbc ang plugz. I am not good with CVS ebuilds and am out of time now... See http://bluetooth-alsa.sourceforge.net/build.html ================================================================================================== From `svn log https://svn.tar.bz/repos/pkalin/branches/damn_bluetooth-alsa/ -r 0:HEAD -v` r136 | Kalin.KOZHUHAROV revbump to btsco-0.5 (seems to portage like downgrade) r137 | Kalin.KOZHUHAROV Purging old ebuilds r138 | Kalin.KOZHUHAROV Inital import of the new ebuild from https://bugs.gentoo.org/attachment.cgi?id=105443 P.S. Removed in -r142 r139 | Kalin.KOZHUHAROV Updating/syncing to http://overlays.gentoo.org/svn/dev/liquidx/net-wireless/btsco-kernel/btsco-kernel-0.41.ebuild Version bump to btsco-0.5; (prviously updated source to .tgz (from tar.gz)) Better usage of linux-mod Added comment for being tested with linux-2.6.19.1 (did NOT check the exact config options though) r140 | Kalin.KOZHUHAROV WTF are people thinking about version numbers!!! add proper inherit statement print ewarn and die die if USE=alsa (not working now) fix/update WANT_AUTOMAKE and WANT_AUTOCONF the Makefile in contrib/skype_bt_hijacker is screwed, do the install manually (it was NOT working apparently in 0.41) r141 | Kalin.KOZHUHAROV fixed/synced to http://overlays.gentoo.org/svn/dev/liquidx/net-wireless/btsco-kernel/btsco-kernel-0.41.ebuild removed DEPEND/RDEPEND and added a die in pkg_setup r142 | Kalin.KOZHUHAROV This (btsco from -r138) is not working properly, provides only btsco; better use net-wireless/bluetooth-alsa-utils ================================================================================================== Some comments to other posters: To comment #70 et all: Peter, why do you think bluetooth-alsa-kernel is not needed? I tried your ebuild from attachment#105443 [details], hoewer no kernel modules were built... Can you use your headset without kernel module? It does NOT seem included in linux-2.6.19.1 comment #73: Hmm, I can incorporate that but no amd64 systems here to test. Anybody willing to write (CVS) ebuilds for libsbc ang plugz ??? Is there an easy way to add my overlay to layman without going to o.g.o ? Please test and somebody try to integrate the init scripts. (In reply to comment #83) > > Is there an easy way to add my overlay to layman without going to o.g.o ? > > Please test and somebody try to integrate the init scripts. > The layman list of overlays is stored inside our CVS I think. For best exposure I think it would be best to add your ebuilds to something like the sunrise overlay. http://www.gentoo-sunrise.org/sunrise Thank you Petteri :-) At the moment, adding it to something like sunrise.g.o is a bit too much probably. But I went on and added support for layman in my overlay! (from http://rsync.tar.bz/README.txt) 0. `emerge app-portage/layman` 1. Add pkalin.xml to layman.cfg (http://rsync.tar.bz/layman.cfg for an example) 2. Add pkalin to your overlays `layman -a pkalin` 3. Enjoy! Can anybody clean this bug by marking old attachments invalid (I have no rights). On another note, I updated the ebuilds as repoman suggested (so attachment #105793 [details] and attachment #105795 [details] are already old. Will wait for some more feedback and repost them here). Created attachment 109657 [details]
net-wireless/libsbc-cvs-20070209.ebuild
*** Bug 170338 has been marked as a duplicate of this bug. *** Created attachment 112916 [details]
libsbc-cvs-20070311.ebuild
Created attachment 112918 [details]
bluetooth-alsa-cvs-20070311.ebuild
Created attachment 112919 [details, diff]
bluez-libs-2.25.diff
Comment on attachment 112918 [details]
bluetooth-alsa-cvs-20070311.ebuild
headset daemons: a2dpd and headsetd
Comment on attachment 112919 [details, diff]
bluez-libs-2.25.diff
patch to compile against bluez-libs-2.25
I have problems with the bluetooth-alsa-kernel ebuild: ----------- * Preparing snd-bt-sco module make[1]: Entering directory `/usr/src/linux-2.6.20-gentoo' CC [M] /var/tmp/portage/net-wireless/bluetooth-alsa-kernel-0.5/work/btsco-0.5/kernel/btsco.o /var/tmp/portage/net-wireless/bluetooth-alsa-kernel-0.5/work/btsco-0.5/kernel/btsco.c: In function 'snd_card_bt_sco_thread': /var/tmp/portage/net-wireless/bluetooth-alsa-kernel-0.5/work/btsco-0.5/kernel/btsco.c:905: warning: implicit declaration of func tion 'try_to_freeze' .----------- modprobe snd-bt-sco FATAL: Error inserting snd_bt_sco (/lib/modules/2.6.20-gentoo/misc/snd-bt-sco.ko): Unknown symbol in module, or unknown parameter (see dmesg) ----------- snd_bt_sco: Unknown symbol try_to_freeze (In reply to comment #93) > I have problems with the bluetooth-alsa-kernel ebuild: Give a try to a new approach from bluetooth-alsa.sourceforge.net without any kernel modules: install libsbc and plugz. could someone please, cleanup this bug? or make a brief outline which ebuilds are needed, and what alsaversion is needed, and if it has to be in kernel or could be used from portage? please? (In reply to comment #95) > could someone please, > cleanup this bug? > or make a brief outline which ebuilds are needed, and what alsaversion is > needed, and if it has to be in kernel or could be used from portage? > please? > oh i forgot, and are there patches which are needed, but not included in 2.6.20 gentoo-sources? we got a problem with this bird. bluetooth alsa radicly changed there approch , and are now supplying a different solution using a user space application (plugz), not the kernel drivers, suggested here. BUT we need to patch the kernel to use plugz. In order for ekiga to work with plugz - you need to patch ekiga. so I am still using this btsco solution, yet other ppl are not putting more effort to this old solution. Hope it helps, Niv (In reply to comment #97) > we got a problem with this bird. > bluetooth alsa radicly changed there approch , and are now supplying a > different solution using a user space application (plugz), not the kernel > drivers, suggested here. > BUT we need to patch the kernel to use plugz. > In order for ekiga to work with plugz - you need to patch ekiga. > so I am still using this btsco solution, yet other ppl are not putting more > effort to this old solution. > Hope it helps, > Niv And if i don't use ekiga for voip (i use actually twinkle, what makes ekiga so special?) i need no more kernel gambling? So what ebuilds are needed for the new way? > (In reply to comment #98) > (In reply to comment #97) > > we got a problem with this bird. > > bluetooth alsa radicly changed there approch , and are now supplying a > > different solution using a user space application (plugz), not the kernel > > drivers, suggested here. > > BUT we need to patch the kernel to use plugz. > > In order for ekiga to work with plugz - you need to patch ekiga. > > so I am still using this btsco solution, yet other ppl are not putting more > > effort to this old solution. > > Hope it helps, > > Niv > > And if i don't use ekiga for voip (i use actually twinkle, what makes ekiga so > special?) i need no more kernel gambling? > So what ebuilds are needed for the new way? > > > Oh Sorry i misunderstood you, we need plugz patches in kernel so where are they i'm currently going to setup an kernel ebuild for my thinkpad anyway, so one patch more or less shouldn't be the problem, maybe such patching only affects the alsa-potion, so the alsa out of portage could be patched easily. kindly reffer to bluetooth-alsa page. all info is there. you will need to patch the bluetooth. pls post your ebuild here. Created attachment 115957 [details]
media-sound/plugz-cvs/plugz-cvs-20070411.ebuild
works fine installing plugz
2.6.20 kernel ebuild with sco patch is in progress, sco patch v3.0 applies fine to full genpatched and suspend2 patched sources
Comment on attachment 115957 [details] media-sound/plugz-cvs/plugz-cvs-20070411.ebuild ><HTML><HEAD/><BODY><PRE># Copyright 1999-2007 Gentoo Foundation ># Distributed under the terms of the GNU General Public License v2 ># $Header: $ > >inherit eutils cvs > >ECVS_SERVER="bluetooth-alsa.cvs.sourceforge.net:/cvsroot/bluetooth-alsa" >ECVS_MODULE="plugz" > >DESCRIPTION="Alsa Plugz for bluetooth audio" >HOMEPAGE="http://bluetooth-alsa.sourceforge.net" > >SRC_URI="" >LICENSE="LGPL-2" >SLOT="0" >KEYWORDS="~x86" >IUSE="" > >DEPEND="dev-util/cvs > >=net-wireless/bluez-libs-3.9" >RDEPEND=">=net-wireless/bluez-libs-3.9" > >S="${WORKDIR}/${ECVS_MODULE}" > >src_compile() { > libtoolize --copy --force > ./bootstrap || die "bootstrap script failed" > econf || die "econf failed" > emake || die "emake failed" >} > >src_install() { > emake DESTDIR="${D}" install || die "emake install failed" >} ></PRE></BODY></HTML> what i just tried is to add the bluez-lib dep also to rdepend (In reply to comment #95) > could someone please, > cleanup this bug? > or make a brief outline which ebuilds are needed, and what alsaversion is > needed, and if it has to be in kernel or could be used from portage? > please? > Some notes: 1. You can download libsbc-cvs-20070311.ebuild, bluetooth-alsa-cvs-20070311.ebuild and bluez-libs-2.25.diff and install this two ebuilds. 2. You don't need any kernel patch if you are using a2pdp only. 3. The ebuilds mentioned compile against bluez-libs-2.25 which is in portage. Created attachment 116063 [details]
sys-kernel/thinkpad-sources/thinkpad-sources-2.6.20.ebuild
This are specially up-patched suspend2 sources including sco_flowcontrol(useflag) patch, the other stuff maybe interesting in matters of harddisk protection or sata hotpluging/swaping.
(In reply to comment #104) > Some notes: > 1. You can download libsbc-cvs-20070311.ebuild, > bluetooth-alsa-cvs-20070311.ebuild and bluez-libs-2.25.diff and install this > two ebuilds. > 2. You don't need any kernel patch if you are using a2pdp only. > 3. The ebuilds mentioned compile against bluez-libs-2.25 which is in portage. > building bluetooth-alsa-cvs with your ebuild fails: i686-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -O2 -march=athlon64 -mno-tls-direct-seg-refs -mmmx -m32 -msse3 -pipe -fomit-frame-pointer -MT pcm_a2dpd.lo -MD -MP -MF .deps/pcm_a2dpd.Tpo -c pcm_a2dpd.c -o pcm_a2dpd.o >/dev/null 2>&1 a2dpd_uinput.c:122:2: Warnung: #warning "NOT building uinput!!" i686-pc-linux-gnu-gcc -shared .libs/pcm_a2dpd.o -lrt -la2dpdcommon /usr/lib/libasound.so -lm -ldl -lpthread /usr/lib/libbluetooth.so -pthread -march=athlon64 -mno-tls-direct-seg-refs -mmmx -m32 -msse3 -Wl,-soname -Wl,libasound_module_pcm_a2dpd.so.0 -o .libs/libasound_module_pcm_a2dpd.so.0.0.0 /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/../../../../i686-pc-linux-gnu/bin/ld: cannot find -la2dpdcommon collect2: ld returned 1 exit status make[3]: *** [libasound_module_pcm_a2dpd.la] Fehler 1 make[3]: *** Warte auf noch nicht beendete Prozesse... i686-pc-linux-gnu-gcc -shared .libs/a2dpd_timer.o .libs/a2dpd_ipc.o .libs/a2dpd_tools.o -lrt /usr/lib/libasound.so -lm -ldl -lpthread /usr/lib/libbluetooth.so -pthread -march=athlon64 -mno-tls-direct-seg-refs -mmmx -m32 -msse3 -Wl,-soname -Wl,liba2dpdcommon.so.0 -o .libs/liba2dpdcommon.so.0.0.0 (cd .libs && rm -f liba2dpdcommon.so.0 && ln -s liba2dpdcommon.so.0.0.0 liba2dpdcommon.so.0) (cd .libs && rm -f liba2dpdcommon.so && ln -s liba2dpdcommon.so.0.0.0 liba2dpdcommon.so) i686-pc-linux-gnu-ar cru .libs/liba2dpdcommon.a a2dpd_timer.o a2dpd_ipc.o a2dpd_tools.o i686-pc-linux-gnu-ranlib .libs/liba2dpdcommon.a creating liba2dpdcommon.la (cd .libs && rm -f liba2dpdcommon.la && ln -s ../liba2dpdcommon.la liba2dpdcommon.la) make[2]: *** [all-recursive] Fehler 1 make[1]: *** [all-recursive] Fehler 1 make: *** [all] Fehler 2 !!! ERROR: net-wireless/bluetooth-alsa-cvs-20070311 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile bluetooth-alsa-cvs-20070311.ebuild, line 37: Called die !!! emake failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log'. (In reply to comment #106) > > !!! A complete build log is located at > '/var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log'. > Please try to build again and on error attach '/var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log' file. (In reply to comment #107) > (In reply to comment #106) > > > > !!! A complete build log is located at > > '/var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log'. > > > > Please try to build again and on error attach > '/var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log' > file. > same problem Created attachment 117200 [details]
/var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log
same problem for me there is a log
(In reply to comment #109) > Created an attachment (id=117200) [edit] > /var/tmp/portage/net-wireless/bluetooth-alsa-cvs-20070311/temp/build.log > > same problem for me there is a log > solved with kernel 2.6.21 (In reply to comment #110) > solved with kernel 2.6.21 I have the same problem (wrt build.log) even with 2.6.21 and I have to put MAKEOPTS="-j1" to src_compile section of ebuild (before emake). I'm trying to compile btsco on amd64 like this page explains : http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset but, I have an error : *** Warning: Linking the shared library libasound_module_pcm_a2dp.la against the *** static library ../sbc/libsbc.a is not portable! x86_64-pc-linux-gnu-gcc -shared .libs/pcm_a2dp.o -L/usr/lib64 ../sbc/libsbc.a /usr/lib64/libasound.so -lm -ldl -lpthread /usr/lib64/libbluetooth.so -march=nocona -Wl,-soname -Wl,libasound_module_pcm_a2dp.so -o .libs/libasound_module_pcm_a2dp.so /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: ../sbc/libsbc.a(sbc.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../sbc/libsbc.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [libasound_module_pcm_a2dp.la] Error 1 make[2]: Leaving directory `/sauve_loc/tmp/portage/net-wireless/btsco-0.41/work/btsco-0.41/alsa-plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/sauve_loc/tmp/portage/net-wireless/btsco-0.41/work/btsco-0.41' make: *** [all] Error 2 I switched from alsa-driver to alsa in the kernel, but nothing changed. btsco-kernel compiles fine, and I can load snd-bt-sco. Created attachment 124658 [details]
net-wireless/libsbc-cvs-20070712.ebuild
Created attachment 124659 [details]
net-wireless/plugz-cvs-20070712
Created attachment 124661 [details]
net-wireless/bluetooth-alsa-utils-0.5-r1
Created attachment 124667 [details, diff]
sco-flowcontrol-v4.3.diff
I was able to compile and run everything on amd64 with bluetooth-alsa-0.5, libsco and plugz from CVS *without* using btsco on kernel 2.6.11. I have documented my experience at gentoo's wiki: http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset#New_versions Please test it and provide feedback. Created attachment 124926 [details]
net-wireless/bluetooth-alsa-utils-0.5-r1
Fix for "test twice before you upload" bug. :-)
Of course, the kernel in #117 is 2.6.22, not 2.6.11... I've got a problem with emerge plugz-cvs-20070712 on amd64 emerge returns: (...) states.c: In function ‘headsetIdleHandleApplConnReq’: states.c:302: error: ‘SDP_NON_BLOCKING’ undeclared (first use in this function) states.c:302: error: (Each undeclared identifier is reported only once states.c:302: error: for each function it appears in.) (...) Maybe I'm doing something wrong? My info: Portage 2.1.2.9 (default-linux/amd64/2007.0, gcc-4.1.1, glibc-2.5-r4, 2.6.20-gentoo-r8 x86_64) ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -msse3 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-march=k8 -msse3 -O2 -pipe" DISTDIR="/home/portage/distfiles" BTW, libsbc-cvs compiled correctly. (In reply to comment #120) > I've got a problem with emerge plugz-cvs-20070712 on amd64 Seems that this is an error in ebuild: the patch bluez-libs-2.25.diff should be applied. Try bluetooth-alsa-cvs-20070311.ebuild instead. Created attachment 126016 [details] net-wireless/plugz-cvs-20070721 Hi all. The attached ebuild superseeds the 20070712 ebuild and patches the source with 'bluez-libs-2.25.diff' (although it compiles just fine here on AMD64 with and without this patch). Please put it in your net-wireless/plugz-cvs folder and put the 'bluez-libs-2.25.diff' (http://bugs.gentoo.org/attachment.cgi?id=112919) in net-wireless/plugz-cvs/files. Regards, Bojan While the howto advices to patch the kernel yourself, and says that the btsco module is not necessary anymore, bluetooth-alsa-utils-0.5-r1 still tries to pull in bluetooth-alsa-kernel-0.5 (which fails to build). Why? Also, the attachments of this bug are becoming a mess and it's hard to see what still works. Thanks anyway 23.08.2007 Release of bluez-libs-3.15 and bluez-utils-3.15 These releases add support for the A2DP profile to stream high quality audio over Bluetooth. It also allows to create RFCOMM based proxy services to export physical serial ports over Bluetooth. So I am quite sure these ebuilds will never make it to the tree after I version bump these to 3.15. I opened bug 190014 for it. Sorry that the work in here never made it. (In reply to comment #124) I will be happy :) Just so that everyone knows I succesfully got A2DP working on my computer using bluez-libs-3.15 and bluez-utils-3.35 following the instructions in http://wiki.bluez.org/wiki/HOWTO/AudioDevices Most of the stuff discussed here bites the new development, so please clean the howtos, just the headsetd might be interesting because I failed to get my sco headset working with twinkel without it, although it works with arecord and mplayer. To me it seems to be elementary to add Autostart=true to /etc/bluetooth/audio.service but afaik it is not the way it should work. Created attachment 145630 [details, diff]
applies to gentoo-sources-2.6.23-r9
Created attachment 183254 [details, diff]
Patch to the kernel gentoo-sources-2.6.28
Patch to the kernel 2.6.28
I'm looking for the btsco patch for the 2.6.30 kernel. Hello,
during an emerge -uDN world I get the following problem:
[blocks B ] net-wireless/bluez ("net-wireless/bluez" is blocking net-wireless/bluez-libs-3.36, net-wireless/bluez-utils-3.36)
[blocks B ] net-wireless/bluez-utils ("net-wireless/bluez-utils" is blocking net-wireless/bluez-4.39-r2)
[blocks B ] net-wireless/bluez-libs ("net-wireless/bluez-libs" is blocking net-wireless/bluez-4.39-r2)
Total: 247 packages (10 upgrades, 126 new, 96 in new slots, 15 reinstalls), Size of downloads: 392,777 kB
Conflict: 3 blocks (3 unsatisfied)
* Error: The above package list contains packages which cannot be
* installed at the same time on the same system.
('ebuild', '/', 'net-wireless/bluez-utils-3.36', 'merge') pulled in by
net-wireless/bluez-utils required by ('installed', '/', 'net-wireless/btsco-0.5', 'nomerge')
('ebuild', '/', 'net-wireless/bluez-4.39-r2', 'merge') pulled in by
net-wireless/bluez required by ('ebuild', '/', 'kde-base/solid-4.3.1', 'merge')
net-wireless/bluez required by ('installed', '/', 'net-libs/libpcap-1.0.0-r2', 'nomerge')
net-wireless/bluez required by ('installed', '/', 'gnome-base/gvfs-1.2.3', 'nomerge')
(and 3 more)
('ebuild', '/', 'net-wireless/bluez-libs-3.36', 'merge') pulled in by
net-wireless/bluez-libs required by ('installed', '/', 'net-wireless/ussp-push-0.9', 'nomerge')
>=net-wireless/bluez-libs-3.36 required by ('ebuild', '/', 'net-wireless/bluez-utils-3.36', 'merge')
net-wireless/bluez-libs required by ('installed', '/', 'net-wireless/btsco-0.5', 'nomerge')
No way to to solve the problem(?).
|
