From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2019-06-05 (meson rpath problem)
Date: Thu, 6 Jun 2019 23:14:55 +0200 [thread overview]
Message-ID: <20190606211454.GA5153@x230> (raw)
In-Reply-To: <5cf8ac0a.1c69fb81.34b7d.30a7SMTPIN_ADDED_MISSING@mx.google.com>
Hi,
> This is the list of Buildroot build failures that occured on
> 2019-06-05, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
> Results for the 'master' branch
> ===============================
> Build failures related to your packages:
> i586 | iputils-s20190515 | http://autobuild.buildroot.net/results/fb698e3e903869978bd5e69d791ec362317b7981
Errors are like
visibility.c:(.text+0x1a): undefined reference to `gpg_strerror'
look like rpath issue similar to [1]. But I have no clue how to fix it in meson,
which iputils uses. There are requirements for it in upstream [2], lack of it
leaded us [3] (and openembedded [4]) to workaround it. But that's obviously not
enough for i586 build. Any tip / hint to fix it?
Kind regards,
Petr
[1] https://patchwork.ozlabs.org/patch/763789/
[2] https://github.com/mesonbuild/meson/issues/2567
[3] https://git.busybox.net/buildroot/tree/package/meson/0001-Only-fix-RPATH-if-install_rpath-is-not-empty.patch
[4] http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/meson/meson/disable-rpath-handling.patch?h=master
next parent reply other threads:[~2019-06-06 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5cf8ac0a.1c69fb81.34b7d.30a7SMTPIN_ADDED_MISSING@mx.google.com>
2019-06-06 21:14 ` Petr Vorel [this message]
2019-06-07 21:52 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-06-05 (meson rpath problem) Fabrice Fontaine
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=20190606211454.GA5153@x230 \
--to=petr.vorel@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