From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: libffi-3.4.7 bug
Date: Mon, 10 Feb 2025 02:35:20 +0000 [thread overview]
Message-ID: <878qqettlj.fsf@gentoo.org> (raw)
Hi!
libffi-3.4.7 unfortunately had a bug snuck in that I'd reported a few
days prior to the release. See https://github.com/libffi/libffi/issues/879.
It causes test failures with Clang at least. Reverting it is non-trivial
because a few build system and test tweaks were made, but you can use
https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/libffi/files/libffi-3.4.7-Revert-Fix-x86-ffi64-calls-with-6-gp-and-some-sse-re.patch?id=913b9ae63372f13deb88137f646213574ae94158
if you like.
thanks,
sam
reply other threads:[~2025-02-10 2:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=878qqettlj.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/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