From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [git commit] package/cmocka: fix build on Thumb classic configurations
Date: Thu, 31 Aug 2023 00:28:37 +0200 [thread overview]
Message-ID: <874jkgnp0q.fsf@48ers.dk> (raw)
In-Reply-To: <20230730221257.C357683D5C@busybox.osuosl.org> (Thomas Petazzoni via buildroot's message of "Mon, 31 Jul 2023 00:12:26 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=5622c76bf42fd29f8dfc231d0fccb623960b3542
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> The cmocka package checks if a toolchain supports the
> -fstack-clash-protection compiler flag, and if it does automatically
> uses it. That flag is not supported by GCC for Thumb1 builds (at least
> as of both GCC 11 and GCC 12). Let's tell cmocka about this by passing
> -DWITH_STACK_CLASH_PROTECTION=OFF in this configuration, as suggested
> by Arnout Vandecappelle.
> Fixes:
> http://autobuild.buildroot.net/results/4044b3a71d3130d934c7a7c0c5badfabb2a97030/
> Signed-off-by: Joel Carlson <JoelsonCarl@gmail.com>
> [Thomas: change the initial patch from Joel to use the suggestion from
> Arnout]
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-30 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 22:12 [Buildroot] [git commit] package/cmocka: fix build on Thumb classic configurations Thomas Petazzoni via buildroot
2023-08-30 22:28 ` 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=874jkgnp0q.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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