From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] brltty: use gcc instead of ld to link shared objects
Date: Wed, 19 Sep 2018 23:45:15 +0200 [thread overview]
Message-ID: <20180919214515.25460-1-fontaine.fabrice@gmail.com> (raw)
Bump to version 5.6 has reintroduced the issue fixed by patch 854093 on
version 5.5.
Indeed, third patch was merged upstream but it was then reverted:
https://github.com/brltty/brltty/commit/9e7d62c869d3c1cbe12dda8b0291a4692c193416
Moreover, since commit 3a2e3f6fa5ef0a210ffeba5ed05c79965d0cc3c7, MKOBJ
was renamed into MKREL. So, instead of patching again brltty, overwrite
MKREL to use "gcc -shrared -o" instead of "ld -r -o".
Fixes:
- http://autobuild.buildroot.org/results/31f682838b3d3b2c7103b5c51f2aba0b89d4f630
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/brltty/brltty.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/brltty/brltty.mk b/package/brltty/brltty.mk
index 21f6877bb8..7b8aff99b4 100644
--- a/package/brltty/brltty.mk
+++ b/package/brltty/brltty.mk
@@ -15,6 +15,9 @@ BRLTTY_LICENSE_FILES = LICENSE-LGPL README
BRLTTY_DEPENDENCIES = $(TARGET_NLS_DEPENDENCIES) host-autoconf host-pkgconf \
$(if $(BR2_PACKAGE_AT_SPI2_CORE),at-spi2-core)
+BRLTTY_CONF_ENV = \
+ brltty_cv_prog_make_object_relocatable="$(TARGET_CC) -shared"
+
BRLTTY_CONF_OPTS = \
--disable-java-bindings \
--disable-lisp-bindings \
--
2.17.1
next reply other threads:[~2018-09-19 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 21:45 Fabrice Fontaine [this message]
2018-09-20 12:11 ` [Buildroot] [PATCH 1/1] brltty: use gcc instead of ld to link shared objects Mario Lang
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=20180919214515.25460-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--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