linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH] build: fix MISC_LDFLAGS typo to fix "--enable-pie"
Date: Thu, 21 Jun 2012 11:45:50 +0200	[thread overview]
Message-ID: <4FE2ED4E.5010503@message-id.googlemail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 313 bytes --]

Hi all,

draconic rules in the openSUSE buildservice found, that executables are
no longer linked with "-pie" and complained about it.

As it turned out, it's a simple typo in acinclude.m4, trivial patch is
attached.

Best regards,

	Stefan
-- 
Stefan Seyfried

"Dispatch war rocket Ajax to bring back his body!"

[-- Attachment #2: 0001-build-fix-MISC_LDFLAGS-typo-to-fix-enable-pie.patch --]
[-- Type: text/x-patch, Size: 747 bytes --]

>From 74cabe5148e7618544ec25f1385aa48454a0ee60 Mon Sep 17 00:00:00 2001
From: Stefan Seyfried <seife+obs@b1-systems.com>
Date: Thu, 21 Jun 2012 11:28:47 +0200
Subject: [PATCH] build: fix MISC_LDFLAGS typo to fix "--enable-pie"

---
 acinclude.m4 |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/acinclude.m4 b/acinclude.m4
index 6505ad3..1d6d736 100644
--- a/acinclude.m4
+++ b/acinclude.m4
@@ -360,7 +360,7 @@ AC_DEFUN([AC_ARG_BLUEZ], [
 	fi
 
 	AC_SUBST([MISC_CFLAGS], $misc_cflags)
-	AC_SUBST([MISC_LDLAGS], $misc_ldlags)
+	AC_SUBST([MISC_LDFLAGS], $misc_ldflags)
 
 	if (test "${usb_enable}" = "yes" && test "${usb_found}" = "yes"); then
 		AC_DEFINE(HAVE_LIBUSB, 1, [Define to 1 if you have USB library.])
-- 
1.7.10.4


             reply	other threads:[~2012-06-21  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  9:45 Stefan Seyfried [this message]
2012-06-21 15:11 ` [PATCH] build: fix MISC_LDFLAGS typo to fix "--enable-pie" Johan Hedberg

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=4FE2ED4E.5010503@message-id.googlemail.com \
    --to=stefan.seyfried@googlemail.com \
    --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;
as well as URLs for NNTP newsgroup(s).