From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/libtomcrypt: compile with -fPIC to enable linking to dynamic libraries/exectuables
Date: Sun, 2 May 2021 12:50:38 +0200 [thread overview]
Message-ID: <20210502105038.19483-2-ps.report@gmx.net> (raw)
In-Reply-To: <20210502105038.19483-1-ps.report@gmx.net>
Fixes:
.../x86_64-buildroot-linux-gnu/bin/ld: .../host/x86_64-buildroot-linux-gnu/sysroot/usr/lib/libtomcrypt.a(md5.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
---
Changes v1 -> v2:
- add -fPIC only for non static builds (suggested by Arnout Vandecappelle)
---
package/libtomcrypt/libtomcrypt.mk | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/libtomcrypt/libtomcrypt.mk b/package/libtomcrypt/libtomcrypt.mk
index 3d166a6854..d1cf552abd 100644
--- a/package/libtomcrypt/libtomcrypt.mk
+++ b/package/libtomcrypt/libtomcrypt.mk
@@ -19,6 +19,10 @@ LIBTOMCRYPT_IGNORE_CVES += CVE-2019-17362
LIBTOMCRYPT_CFLAGS = -I./src/headers $(TARGET_CFLAGS) -DLTC_SOURCE -DLTM_DESC
+ifeq ($(BR2_STATIC_LIBS),)
+LIBTOMCRYPT_CFLAGS += -fPIC
+endif
+
define LIBTOMCRYPT_BUILD_CMDS
$(TARGET_MAKE_ENV) $(MAKE) -C $(@D) $(TARGET_CONFIGURE_OPTS) CFLAGS="$(LIBTOMCRYPT_CFLAGS)"
endef
--
2.31.1
next prev parent reply other threads:[~2021-05-02 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 10:50 [Buildroot] [PATCH v2 1/2] package/libtomcrypt: add pkgconfig support Peter Seiderer
2021-05-02 10:50 ` Peter Seiderer [this message]
2021-05-04 20:17 ` [Buildroot] [PATCH v2 2/2] package/libtomcrypt: compile with -fPIC to enable linking to dynamic libraries/exectuables Arnout Vandecappelle
2021-05-08 9:35 ` Peter Korsgaard
2021-05-04 20:18 ` [Buildroot] [PATCH v2 1/2] package/libtomcrypt: add pkgconfig support Arnout Vandecappelle
2021-05-06 20:16 ` Peter Seiderer
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=20210502105038.19483-2-ps.report@gmx.net \
--to=ps.report@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.