From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ntpsec: fix build without stack-protector
Date: Sat, 25 Feb 2023 10:49:26 +0100 [thread overview]
Message-ID: <20230225104926.28b9bb48@windsurf> (raw)
In-Reply-To: <20230224105148.1780818-1-fontaine.fabrice@gmail.com>
On Fri, 24 Feb 2023 11:51:48 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure without stack-protector raised since the
> addition of the package in commit
> 27b8d0ba8c4004819e092fb81c0f64f284b3aa4a:
>
> Checking for library ssp : not found
> Checking for library ssp_nonshared : not found
> Checking if C compiler supports -fstack-protector-all : yes
>
> [...]
>
> The configuration failed
> (complete log in /home/autobuild/autobuild/instance-2/output-1/build/ntpsec-1_2_2/build/config.log)
>
> Fixes:
> - http://autobuild.buildroot.org/results/f38abc6b7f8464836231192cfe078a5b27319a8a
> - http://autobuild.buildroot.org/results/62be818e2f2eac07b4a2de6f4a8898cc4cc05b1f
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...pt-fix-build-without-stack-protector.patch | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
> create mode 100644 package/ntpsec/0002-wscript-fix-build-without-stack-protector.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-25 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 10:51 [Buildroot] [PATCH 1/1] package/ntpsec: fix build without stack-protector Fabrice Fontaine
2023-02-25 9:49 ` Thomas Petazzoni via buildroot [this message]
2023-03-13 17:09 ` Peter Korsgaard
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=20230225104926.28b9bb48@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--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