From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] [PATCH] Fix 64 configuration
Date: Wed, 14 Nov 2007 23:53:46 -0300 [thread overview]
Message-ID: <473BB4BA.4030102@aircable.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Hello everyone,
It's been about 1 month since I got my 64 bits laptop, and after a hole
month I started to figure out why the he## I couldn't get the audio
service working on it. Or the pan service, or the serial service, or
what ever service you might think off.
I was always getting: dbus.exceptions.DBusException:
org.bluez.Error.Failed: Exec format error
When ever I asked dbus to register a new server.
After a long trial and error, I discovered that by default bluez was
installing all the services to ${prefix}/lib instead of ${prefix}/lib64.
Here's a little patch that fixes that problem. I'm not sure if I fixed
the problem in the best way, I haven't ever used auto tools for over 10
seconds, so I might have broken something. I tested, it builds, and then
when I make the install it puts the files into lib64.
The patch was made against the latest cvs version.
Thanks,
Manuel Naranjo
Wireless Cables Inc.
www.aircable.net
[-- Attachment #2: bluez-utils_64bits.cvs.patch --]
[-- Type: text/x-patch, Size: 389 bytes --]
47,49c47,50
<
< if (test "${libdir}" = '${exec_prefix}/lib'); then
< libdir="${prefix}/lib"
---
>
> dnl if lib64 is present then we use it
> if (test -d "${prefix}/lib64" ); then
> libdir="${prefix}/lib64"
51c52,57
<
---
>
> dnl and then only if ${libdir} keeps beeing empty we use lib
> if ( test -z "${libdir}" ) ; then
> libdir="${prefix}/lib"
> fi
>
68a75
>
[-- Attachment #3: Type: text/plain, Size: 314 bytes --]
-------------------------------------------------------------------------
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/
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-11-15 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 2:53 Manuel Naranjo [this message]
2007-11-15 15:18 ` [Bluez-devel] [PATCH] Fix 64 configuration Bastien Nocera
2007-11-15 16:33 ` Manuel Naranjo
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=473BB4BA.4030102@aircable.net \
--to=manuel@aircable.net \
--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