From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Sergio Prado <sergio.prado@e-labworks.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/snort: fix sparc build with BR2_OPTIMIZE_FAST
Date: Mon, 15 Aug 2022 14:37:03 +0200 [thread overview]
Message-ID: <20220815143703.4aebe34f@windsurf> (raw)
In-Reply-To: <20220809184427.2469515-1-fontaine.fabrice@gmail.com>
On Tue, 9 Aug 2022 20:44:27 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following sparc build failure with BR2_OPTIMIZE_FAST raised
> since bump to version 2.9.19 in commit
> 65ed981ce0135379b7faeb69519f4e3e666c0717:
>
> cc1: error: argument to '-O' should be a non-negative integer, 'g', 's' or 'fast'
>
> Fixes:
> - http://autobuild.buildroot.org/results/e1a330e1a899fcdf4900e9156d62c90813321e30
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/snort/0008-Fix-NO-OPTIMIZE.patch | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
> create mode 100644 package/snort/0008-Fix-NO-OPTIMIZE.patch
To be honest, I find it pretty crappy that the snort build system
forcefully disables optimizations on SPARC. But oh well, I don't care
much about SPARC, so: 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:[~2022-08-15 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 18:44 [Buildroot] [PATCH 1/1] package/snort: fix sparc build with BR2_OPTIMIZE_FAST Fabrice Fontaine
2022-08-15 12:37 ` Thomas Petazzoni via buildroot [this message]
2022-09-16 12:23 ` 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=20220815143703.4aebe34f@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=sergio.prado@e-labworks.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