From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] package/strace --enable-mpers=no
Date: Sun, 06 Sep 2020 09:34:07 +0300 [thread overview]
Message-ID: <87k0x72z34.fsf@tarshish> (raw)
In-Reply-To: <CAEyMn7a8hML1-mFD11YMWoZ7VM+YHLNJQyBJEpg5x2jJx2qXRw@mail.gmail.com>
Hi Heiko,
On Sun, Sep 06 2020, Heiko Thiery wrote:
> I faced an issue when building strace for aarch64 on my host where a
> 32bit arm toolchain is installed. As discussed with Brandon on IRC
> strace seems to find the 32bit toolchain because of the
> --enable-mpers=check option and fails with that.
>
> Do you think it makes sense to set --enable-mpers=no since buildroot
> does not support multi personality toolchains?
>
> [1] https://pastebin.com/8uaFHgyP
> [2] https://pastebin.com/GeSYYvnB
I never really got around to fully understand strace mpers handling. I
have been bitten by mpers in the past (commit fc0d31caeedb).
Buildroot built strace might run on external executable binaries. If
this functionality is useful, I don't think we should just disable it.
Why didn't the autobuilders catch this failure?
James' autobuilder does show a different mpers related build failure:
http://autobuild.buildroot.net/?reason=strace-5.7
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2020-09-06 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 21:17 [Buildroot] package/strace --enable-mpers=no Heiko Thiery
2020-09-06 6:34 ` Baruch Siach [this message]
2020-09-07 17:58 ` Heiko Thiery
2020-09-07 18:44 ` Heiko Thiery
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=87k0x72z34.fsf@tarshish \
--to=baruch@tkos.co.il \
--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