From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bogdan Radulescu <bogdan@nimblex.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/nettest: needs SSE2 on i386
Date: Tue, 13 Oct 2026 23:02:16 +0200 [thread overview]
Message-ID: <as6cUED1OoRn2HyM@windsurf> (raw)
In-Reply-To: <20261013095835.3845366-1-bogdan@nimblex.net>
On Tue, Oct 13, 2026 at 12:58:35PM +0300, Bogdan Radulescu wrote:
> nettest depends, through rustls, quinn and rcgen, on the ring crate,
> which refuses to build for 32-bit x86 targets without SSE and SSE2:
>
> error[E0080]: evaluation panicked: assertion failed: cfg!(target_feature = "sse") && cfg!(target_feature = "sse2")
> --> .../VENDOR/ring/src/cpu/intel.rs:26:9
>
> This affects i586 and i686-class CPUs that lack SSE2
> Make nettest depend on SSE2 support when building for i386.
>
> Fixes: https://autobuild.buildroot.org/results/d04f770538412bee77851142ee007f2ff107e0ec
> Fixes: 36fa00354730 ("package/nettest: new package")
> Signed-off-by: Bogdan Radulescu <bogdan@nimblex.net>
Applied to master, thanks a lot!
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-10-13 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 18:57 [Buildroot] [PATCH] package/nettest: not available for the i586 Rust targets Bogdan Radulescu
2026-10-13 8:05 ` Thomas Petazzoni via buildroot
2026-10-13 10:04 ` Bogdan Rădulescu
2026-10-13 9:58 ` [Buildroot] [PATCH v2] package/nettest: needs SSE2 on i386 Bogdan Radulescu
2026-10-13 21:02 ` Thomas Petazzoni via buildroot [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=as6cUED1OoRn2HyM@windsurf \
--to=buildroot@buildroot.org \
--cc=bogdan@nimblex.net \
--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