public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sourceware at mattwhitlock dot name" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27318] glibc fails to load binaries when built with -march=sandybridge: CPU ISA level is lower than required Date: Tue, 27 Apr 2021 17:47:55 +0000 [thread overview] Message-ID: <bug-27318-131-PhtD3KEaHd@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27318-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27318 --- Comment #12 from Matt Whitlock <sourceware at mattwhitlock dot name> --- Never mind. The problem on Gentoo is that the Gentoo ebuild is forcing libc_cv_include_x86_isa_level=no on the configure command line (as a vestigial workaround to this bug), and that's causing the configure test to be skipped, thereby skipping over the initialization of libc_cv_have_x86_lahf_sahf and libc_cv_have_x86_movbe. I've reported that problem to Gentoo. Apologies for the noise here. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-27 17:47 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-02 19:48 [Bug dynamic-link/27318] New: " slyfox at inbox dot ru 2021-02-02 20:19 ` [Bug dynamic-link/27318] " fweimer at redhat dot com 2021-02-02 20:54 ` slyfox at inbox dot ru 2021-02-02 21:11 ` hjl.tools at gmail dot com 2021-02-02 21:19 ` hjl.tools at gmail dot com 2021-02-02 21:52 ` hjl.tools at gmail dot com 2021-02-08 1:46 ` xry111 at mengyan1223 dot wang 2021-02-08 2:27 ` xry111 at mengyan1223 dot wang 2021-02-08 7:18 ` slyfox at inbox dot ru 2021-03-01 14:54 ` schwab@linux-m68k.org 2021-03-06 16:49 ` hjl.tools at gmail dot com 2021-03-16 22:28 ` sam at gentoo dot org 2021-04-27 17:16 ` sourceware at mattwhitlock dot name 2021-04-27 17:22 ` fweimer at redhat dot com 2021-04-27 17:47 ` sourceware at mattwhitlock dot name [this message] 2023-08-17 4:18 ` sam at gentoo dot org
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=bug-27318-131-PhtD3KEaHd@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).