LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-25-2009, 06:35 AM   #16
dolphin77
Member
 
Registered: May 2009
Posts: 200

Rep: Reputation: 54

in obexfs.SlackBuilds should be :
/sbin/makepkg -l y -c n $TMP/$PRGNAM-$VERSION-$ARCH-$BUILD.txz
instead of
/sbin/makepkg -l y -c n $TMP/$NAME-$VERSION-$ARCH-$BUILD.txz}

in openobex.SlackBuilds should be
tar xvf $CWD/${PKGNAM}-$VERSION.tar.gz || exit 1
instead of
tar xvf $CWD/${PKGNAM}-$VERSION.tar.bz2 || exit 1


are there any additional dependencies? What is the correct build/install order?

obexftp and obex-data-server doesn't build for me. It dies with some errors.
 
Old 11-25-2009, 06:47 AM   #17
drgr33n
LQ Newbie
 
Registered: Dec 2008
Distribution: Slackware 13-current x86_64
Posts: 13

Original Poster
Rep: Reputation: 1
Ok dolphin77 I'm looking into this now. What error's are you getting ??
 
Old 11-25-2009, 07:06 AM   #18
dolphin77
Member
 
Registered: May 2009
Posts: 200

Rep: Reputation: 54
sh obex-data-server.SlackBuild

Code:
        mv -f $depbase.Tpo $depbase.Po
gcc -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include   -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/ImageMagick     -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include       -O2 -fPIC   -o src/obex-data-server src/ods-bluez.o src/ods-usb.o src/ods-capabilities.o src/ods-common.o src/ods-error.o src/ods-folder-listing.o src/ods-imaging-helpers.o src/ods-main.o src/ods-marshal.o src/ods-manager.o src/ods-logging.o src/ods-obex.o src/ods-server.o src/ods-server-session.o src/ods-session.o -lgobject-2.0 -lglib-2.0   -pthread -lgthread-2.0 -lrt -lglib-2.0 -lMagickWand -lMagickCore   -lusb   -ldbus-glib-1 -lgobject-2.0 -lglib-2.0 -ldbus-1   -lbluetooth   -lopenobex -lbluetooth
src/ods-obex.o: In function `ods_obex_send':
ods-obex.c:(.text+0x7d): undefined reference to `OBEX_ObjectGetCommand'
collect2: ld returned 1 exit status
make[1]: *** [src/obex-data-server] Error 1
make: *** [all] Error 2
sh obexftp.SlackBuild:

Code:
make[3]: Leaving directory `/tmp/obexftp-0.23/swig/python'
Making all in ruby
make[3]: Entering directory `/tmp/obexftp-0.23/swig/ruby'
PREFIX=/usr /usr/bin/ruby extconf.rb --with-obexftp-include=../..
checking for OBEX_Init() in -lopenobex... yes
checking for bfb_io_open() in -lbfb... yes
checking for cobex_ctrans() in -lmulticobex... yes
checking for obexftp_open() in -lobexftp... no
obex libs not found
make -fMakefile.ruby
make[4]: Entering directory `/tmp/obexftp-0.23/swig/ruby'
make[4]: Makefile.ruby: No such file or directory
make[4]: *** No rule to make target `Makefile.ruby'.  Stop.
make[4]: Leaving directory `/tmp/obexftp-0.23/swig/ruby'
make[3]: *** [obexftp.so] Error 2
make[3]: Leaving directory `/tmp/obexftp-0.23/swig/ruby'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/obexftp-0.23/swig'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/obexftp-0.23'
make: *** [all] Error 2
 
Old 11-25-2009, 08:33 AM   #19
MS3FGX
Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 351Reputation: 351Reputation: 351Reputation: 351
Quote:
Originally Posted by drgr33n View Post
I don't know if I will carry on with kbluetooth or also go down the blueman route?. kbluetooth seemed fine on my system but as I'm testing I'm finding more than a few issues as its far from a finished project.
Blueman is certainly more mature, and in the long run is a better choice as it will work in the other WMs (like XFCE) without having to install KDE.

I have been running BlueZ 4.x on Slackware 13 for awhile now, and all that is really required is a competent front-end (which simply wasn't available for the stable Slackware 13 release).

I am surprised to hear Blueman is working, I have tried unsuccessfully to get it to run on Slackware 13 a few times now, it has always failed with obscure errors that the developers told me was due to the recent builds requiring a newer GTK2 release.
 
Old 11-25-2009, 12:50 PM   #20
drgr33n
LQ Newbie
 
Registered: Dec 2008
Distribution: Slackware 13-current x86_64
Posts: 13

Original Poster
Rep: Reputation: 1
Hey again guys,

Everything's been fixed now WOOP WOOP Also kbluetooth has been updated to its git version. Should solve the dodgy icon.

As for blueman, more packages MS3FGX was right gtk+2 need updating plus libnotify, notification-daemon and notify-python are needed. I'm busy for a few days I'l take a look then.

EDIT: I've got blueman working by upgrading glib, gtk+2 and pango to their latest versions. Also found a handy script that adds browsing support to blueman via dolphin. I'll add all this in the next few days.

@ dolphin77

Do you have ruby installed and are you installing the new openobex package before building obex-data-server ?

Cheers,

Zarren

Last edited by drgr33n; 11-25-2009 at 03:24 PM.
 
Old 12-02-2009, 05:57 PM   #21
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 50
To anyone interested,

I finally got this to build

order of events:

remove libusb-0.1.12
build and install in this order:
libusb-1.0.6
libusb-compat-0.1.3
openobex-1.5
bluez-4.58
obex-data-server-0.4.5
obexd-0.19
obexftp-0.23
obexfs-0.12
kbluetooth-git

fixed errors in slackbuilds that dolphin77 points out

I downloaded the libusb-compat package from the libusb.org site, removed the stock libusb, and installed libusb-1.0.6 and libusb-compat-0.1.3 (do not know if this was strictly necessary, but it is working well for me, ymmv).

despite upgrading ruby, obexftp would not build without adding --disable-ruby in the configure options

tobyl
 
Old 12-02-2009, 06:11 PM   #22
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Quote:
Originally Posted by tobyl View Post
To anyone interested,

I finally got this to build

order of events:

remove libusb-0.1.12
build and install in this order:
libusb-1.0.6
libusb-compat-0.1.3
openobex-1.5
bluez-4.58
obex-data-server-0.4.5
obexd-0.19
obexftp-0.23
obexfs-0.12
kbluetooth-git

fixed errors in slackbuilds that dolphin77 points out

I downloaded the libusb-compat package from the libusb.org site, removed the stock libusb, and installed libusb-1.0.6 and libusb-compat-0.1.3 (do not know if this was strictly necessary, but it is working well for me, ymmv).

despite upgrading ruby, obexftp would not build without adding --disable-ruby in the configure options
Re libusb updates, I've got those queued up here for -current sooner or later, but they weren't necessary for building kbluetooth - was there some other reason you wanted those?

Re obexftp, I experienced the same here with ruby - I just disabled it and made a note about it. If anyone cares, they'll figure out how to make it work. :-)
 
Old 12-03-2009, 10:32 AM   #23
drgr33n
LQ Newbie
 
Registered: Dec 2008
Distribution: Slackware 13-current x86_64
Posts: 13

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by tobyl View Post

I downloaded the libusb-compat package from the libusb.org site, removed the stock libusb, and installed libusb-1.0.6 and libusb-compat-0.1.3 (do not know if this was strictly necessary, but it is working well for me, ymmv).

despite upgrading ruby, obexftp would not build without adding --disable-ruby in the configure options

tobyl
I'm sorry I didn't get any error's while building obexftp ? Maybe I have something else installed that is necessary to build obexftp with ruby support. Maybe rails ?? I'll look into this later this evening.

libusb is not needed for building kbluetooth, the reason it was added to the packages is because udev would not start the bluetooth daemon without upgrading libusb (on my machine) ??
 
Old 12-03-2009, 01:55 PM   #24
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 50
Robby,
I upgraded libusb simply because I couldn't get kbluetooth to work, and was trying all the options. I am guilty of trying several changes at once - hence I did not know for certain whether the libusb changes contributed to my eventual success.
When I saw libusb-1 in drgr33n's package list, I assumed incorrectly that a) it was required, and b) that it replaced libusb-0.1. So I removed libusb-0.1 and installed libusb-1.

Subsequent attempts at building one of the other packages errored on libusb-0.1 not being present, so I installed the compat package.

Silly really, but it was caused by the fact that a lot of packages have next to useless INSTALL and README files these days, and the dependencies are often not listed.

tobyl
 
Old 12-03-2009, 09:12 PM   #25
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Interesting; kbluetooth still doesn't work for me, and I've got all of the above (and then some) done here locally. We're eventually going to get all or most or at least some of this out into the -current tree, so maybe some more eyes looking at it will figure out the missing bits...
 
Old 12-04-2009, 05:21 AM   #26
drgr33n
LQ Newbie
 
Registered: Dec 2008
Distribution: Slackware 13-current x86_64
Posts: 13

Original Poster
Rep: Reputation: 1
Quote:
Originally Posted by rworkman View Post
Interesting; kbluetooth still doesn't work for me, and I've got all of the above (and then some) done here locally. We're eventually going to get all or most or at least some of this out into the -current tree, so maybe some more eyes looking at it will figure out the missing bits...
When all said and done I'm still sticking to kbluetooth4 is still quite abit buggy. it requires a solid update amongst other things.

After trialing kbluetooth and blueman I think blueman is a much better option !
 
Old 12-08-2009, 07:15 AM   #27
JeanSimeoni
LQ Newbie
 
Registered: Dec 2009
Location: Valinhos, São Paulo, Brazil
Posts: 1

Rep: Reputation: 0
Only a gray icon and no adapter found...

Hi guys,

First, thanks for the tutorial. I was able to compile and install everything, but when I start the kbluetooth4 I only got a gray tray icon and no options enabled in the menu...

I tried to run the kbluetooth4-devicemanager (I don't know if this makes sense for a test ), but I only got a "No Bluetooth Adapter found!" message.

My adapter is listed as:
- Bluetooth Dongle (HCI mode)
- Cambridge Silicon Radio, Ltd

Does anybody have an idea of what I need to do to have this adapter working, or how/where can I get more information about what may be preventing the adapter for being found by kdebluetooth4?

Thanks a lot!
Jean
 
Old 12-09-2009, 02:20 PM   #28
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 50
Hi JeanSimeoni,

Not sure if this is your problem, but it sounds like

you need to run /usr/sbin/bluetoothd (as root)

also try removing your adapter and plugging it in again, or running

udevadm trigger

which will cause udev to scan your system, as I think udev misses the usb dongle on bootup

I am assuming that you have not got /etc/rc.d/rc.bluetooth executable (its somewhat outdated for our purposes)

tobyl
 
Old 12-10-2009, 08:20 AM   #29
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
I'm not sure what's going on with the adapters not triggering "bluetoothd --udev" at system startup. I asked Marcel (the lead dev) in #bluez on freenode if he'd had any other reports of that, and he said no, so this is a bit bothersome. I don't think udev is the problem, because I'm fairly certain that you guys are not running the same udev that I am I'm on 149 here locally, and I suspect that most (all?) of you are still on 141 from 13.0. I seem to recall that the problem did NOT exist in bluez-4.56, but I haven't had a chance yet to downgrade and test that. Assuming it does start properly there, then I've got a git checkout of bluez ready for bisecting :-)

The only other real problem that I've experienced is that one of the blueman components (related to the applet) that's started when a bluetooth adapter is hotplugged seems to occasionally go crazy and start doing massive disk I/O. Unfortunately, I've got too many other things on my plate right now to spend too much time troubleshooting that, and I don't want to report a bug to upstream blueman without more information...
 
Old 12-11-2009, 10:40 AM   #30
drgr33n
LQ Newbie
 
Registered: Dec 2008
Distribution: Slackware 13-current x86_64
Posts: 13

Original Poster
Rep: Reputation: 1
I'm on it rworkman stand by for more info !!

EDIT:

Hey guys,

@ JeanSimeoni

Are you using a usb device or is it built in ? If its built in hotplugging will not work for this device and you have to start the bluetooth services manually.


@ rworkman

It seems the I/O interference is down to blueman flooding udev ?? the trunk version of blueman seems to have solved this one ? Got a poker match to attend to .

Sorry I haven't been keeping up but i have had two exams in the last 3 weeks and things have been hectic. I'l try to get some more done over the weekend.

Muchos Gracias,

Zarren

Last edited by drgr33n; 12-11-2009 at 01:01 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Making Slackware and Slackware Derivative Linux Distros Speak Your Language LXer Syndicated Linux News 0 01-29-2009 12:30 AM
Kbluetooth4 not working, any alternatives? HackTidus Linux - Software 2 01-06-2009 03:52 AM
About Slackware 9.1 boot disk?? ftp://ftp.kpn.be/pub/linux/slackware/slackware-9.1-is AL3OMDAH Slackware 4 04-18-2007 09:54 AM


All times are GMT -5. The time now is 11:10 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration