From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libpcap: fix sparc64 build, -fPIC required
Date: Tue, 3 Nov 2015 18:17:35 +0100 [thread overview]
Message-ID: <20151103171735.GA32079@waldemar-brodkorb.de> (raw)
Should fix following autobuilder issues:
http://autobuild.buildroot.net/results/e79353496aa91848c76f15c561efdd84476c20ac/
http://autobuild.buildroot.net/results/a859ecb153838837e9a73b47ed7e1105d6be55ac/
http://autobuild.buildroot.net/results/f2ce1899a1144bec23fb25f4ce36dc78d768f8a8/
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/libpcap/libpcap.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libpcap/libpcap.mk b/package/libpcap/libpcap.mk
index eb21fa9..e6dacc8 100644
--- a/package/libpcap/libpcap.mk
+++ b/package/libpcap/libpcap.mk
@@ -55,8 +55,8 @@ else
LIBPCAP_CONF_OPTS += --without-libnl
endif
-# microblaze needs -fPIC instead of -fpic
-ifeq ($(BR2_microblaze),y)
+# microblaze/sparc64 needs -fPIC instead of -fpic
+ifeq ($(BR2_microblaze)$(BR2_sparc64),y)
LIBPCAP_CFLAGS += -fPIC
endif
--
1.7.10.4
next reply other threads:[~2015-11-03 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 17:17 Waldemar Brodkorb [this message]
2015-11-03 18:56 ` [Buildroot] [PATCH] libpcap: fix sparc64 build, -fPIC required Baruch Siach
2015-11-03 19:51 ` Thomas Petazzoni
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=20151103171735.GA32079@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@busybox.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