From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: help libbacktrace detection of sync builtins
Date: Sat, 03 Oct 2020 08:09:21 +0200 [thread overview]
Message-ID: <87tuvbzvqm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200925090451.1407258-1-romain.naour@gmail.com> (Romain Naour's message of "Fri, 25 Sep 2020 11:04:51 +0200")
>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:
> From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> The logic in libbacktrace/configure.ac to detect if __sync builtins
> are available assumes they are as soon as target_subdir is not
> empty, i.e when cross-compiling. However, some platforms do not have
> __sync builtins, so help the configure script a bit.
> "libbacktrace_cv_sys_sync=no" is lost when it is added to
> HOST_GCC_COMMON_CONF_ENV because the environment is not exported
> when executing the libbacktrace configure script.
> Use target_configargs to force "libbacktrace_cv_sys_sync=no" when
> executiong the libbacktrace configure script.
> Fixes:
> https://gitlab.com/bootlin/toolchains-builder/-/jobs/729359681
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> [Romain: use target_configargs="libbacktrace_cv_sys_sync=no"]
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
Committed to 2020.02.x, 2020.05.x and 2020.08.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2020-10-03 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 9:04 [Buildroot] [PATCH] package/gcc: help libbacktrace detection of sync builtins Romain Naour
2020-09-30 21:02 ` Thomas Petazzoni
2020-10-03 6:09 ` Peter Korsgaard [this message]
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=87tuvbzvqm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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