From: David Sainty <david.sainty@dtsp.co.nz>
To: linux-bluetooth@vger.kernel.org
Subject: Minor error in BlueZ 4.8 Makefile.am can break build
Date: Mon, 29 Sep 2008 17:53:29 +1300 [thread overview]
Message-ID: <48E05F49.7070501@dtsp.co.nz> (raw)
[-- Attachment #1: Type: text/plain, Size: 110 bytes --]
There's a missing backslash in the plugins/Makefile.am file in the 4.8
release (see patches).
Cheers,
Dave
[-- Attachment #2: patch-aa --]
[-- Type: text/plain, Size: 764 bytes --]
$NetBSD$
Fix for missing backslash in Makefile.am.
--- plugins/Makefile.in.orig 2008-09-29 16:15:13.007562391 +1300
+++ plugins/Makefile.in 2008-09-29 16:15:41.627994124 +1300
@@ -235,7 +235,9 @@
AM_LDFLAGS = -module -avoid-version -no-undefined \
-export-symbols-regex bluetooth_plugin_desc
-AM_CFLAGS = @BLUEZ_CFLAGS@ @DBUS_CFLAGS@ @GLIB_CFLAGS@
+AM_CFLAGS = @BLUEZ_CFLAGS@ @DBUS_CFLAGS@ @GLIB_CFLAGS@ \
+ @GDBUS_CFLAGS@ @NETLINK_CFLAGS@
+
INCLUDES = -I$(top_srcdir)/common -I$(top_srcdir)/src
MAINTAINERCLEANFILES = Makefile.in
all: all-am
@@ -539,7 +541,6 @@
pdf pdf-am ps ps-am tags uninstall uninstall-am \
uninstall-pluginLTLIBRARIES
- @GDBUS_CFLAGS@ @NETLINK_CFLAGS@
all-local:
@$(LN_S) -f $(top_srcdir)/input/.libs/input.so
[-- Attachment #3: gdbus.diff --]
[-- Type: text/x-diff, Size: 455 bytes --]
--- plugins/Makefile.am.orig 2008-09-29 16:09:39.972538634 +1300
+++ plugins/Makefile.am 2008-09-29 16:09:48.862672739 +1300
@@ -34,7 +34,7 @@
AM_LDFLAGS = -module -avoid-version -no-undefined \
-export-symbols-regex bluetooth_plugin_desc
-AM_CFLAGS = @BLUEZ_CFLAGS@ @DBUS_CFLAGS@ @GLIB_CFLAGS@
+AM_CFLAGS = @BLUEZ_CFLAGS@ @DBUS_CFLAGS@ @GLIB_CFLAGS@ \
@GDBUS_CFLAGS@ @NETLINK_CFLAGS@
INCLUDES = -I$(top_srcdir)/common -I$(top_srcdir)/src
next reply other threads:[~2008-09-29 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 4:53 David Sainty [this message]
2008-09-29 6:33 ` Minor error in BlueZ 4.8 Makefile.am can break build 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=48E05F49.7070501@dtsp.co.nz \
--to=david.sainty@dtsp.co.nz \
--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