From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: Fix building bluez-gnome in a custom prefix
Date: Wed, 24 Sep 2008 14:03:43 -0700 [thread overview]
Message-ID: <1222290223.10497.183.camel@snoogens.fab.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: 0001-Fix-building-in-a-custom-prefix.patch --]
[-- Type: text/x-patch, Size: 686 bytes --]
>From 987348e19a9b2cab05666165d85b19d8eb06f0c3 Mon Sep 17 00:00:00 2001
From: Bastien Nocera <hadess@hadess.net>
Date: Wed, 24 Sep 2008 11:34:02 -0700
Subject: [PATCH] Fix building in a custom prefix
We need to pass ACLOCAL_FLAGS to aclocal, otherwise it'll be ignored
Patch from Michael Monreal <michael.monreal@gmx.net>
---
bootstrap | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/bootstrap b/bootstrap
index eeb7635..5def899 100755
--- a/bootstrap
+++ b/bootstrap
@@ -1,6 +1,6 @@
#!/bin/sh
-aclocal && \
+aclocal $ACLOCAL_FLAGS && \
autoheader && \
intltoolize --automake --copy --force &&
automake --add-missing --copy && \
--
1.6.0.1
next reply other threads:[~2008-09-24 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 21:03 Bastien Nocera [this message]
2008-09-27 4:25 ` Fix building bluez-gnome in a custom prefix Marcel Holtmann
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=1222290223.10497.183.camel@snoogens.fab.redhat.com \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
/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