From: Manuel Naranjo <manuel@aircable.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Fix 64 configuration
Date: Thu, 15 Nov 2007 13:33:05 -0300 [thread overview]
Message-ID: <473C74C1.2000105@aircable.net> (raw)
In-Reply-To: <1195139936.3140.98.camel@cookie.hadess.net>
[-- Attachment #1: Type: text/plain, Size: 142 bytes --]
Oops!! Sorry.
> Please use "diff -up" to generate your patches. There's not even a
> filename in the diff you posted.
>
>
Here it's again.
[-- Attachment #2: bluez-utils_64bits.cvs.patch --]
[-- Type: text/x-patch, Size: 637 bytes --]
--- acinclude.m4.orig 2007-11-14 23:40:12.000000000 -0300
+++ acinclude.m4 2007-11-15 12:22:48.000000000 -0300
@@ -44,11 +44,17 @@ AC_DEFUN([AC_INIT_BLUEZ], [
prefix="${ac_default_prefix}"
fi
-
- 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"
fi
-
+
+ dnl and then only if ${libdir} keeps beeing empty we use lib
+ if ( test -z "${libdir}" ) ; then
+ libdir="${prefix}/lib"
+ fi
+
if (test "$sysconfdir" = '${prefix}/etc'); then
configdir="${prefix}/etc/bluetooth"
else
[-- 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
prev parent reply other threads:[~2007-11-15 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 2:53 [Bluez-devel] [PATCH] Fix 64 configuration Manuel Naranjo
2007-11-15 15:18 ` Bastien Nocera
2007-11-15 16:33 ` Manuel Naranjo [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=473C74C1.2000105@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