public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/94998] New: GCC 10 won't configure for host=x86, build!=host, linker=bfd due to CET Date: Fri, 08 May 2020 08:40:21 +0000 [thread overview] Message-ID: <bug-94998-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94998 Bug ID: 94998 Summary: GCC 10 won't configure for host=x86, build!=host, linker=bfd due to CET Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: harald at gigawatt dot nl Target Milestone: --- Configuring libiberty fails when gcc is configured as ../gcc-10.1.0/configure --build=x86_64-forcecross-linux-gnu --host=x86_64-pc-linux-gnu --enable-languages=c,c++ CC='gcc-10.1.0 -fuse-ld=bfd' CXX='g++-10.1.0 -fuse-ld=bfd' (This is a shorter simplified configure line to make it easier to reproduce the problem, not the one I was originally using. Please ignore the fact that it's weird to trick the configure script into thinking it's cross-compiling when it's not.) It fails like so: [...] checking for CET support... configure: error: in `/h/gcc-10.1.0-build/libiberty': configure: error: cannot run test program while cross compiling See `config.log' for more details make[1]: *** [Makefile:7986: configure-libiberty] Error 1 make[1]: Leaving directory '/h/gcc-10.1.0-build' make: *** [Makefile:955: all] Error 2 It works with gold because the linker options '-Wl,-z,ibt,-z,shstk' are not accepted by gold (at least in binutils 2.34), so it never gets to the point where it tries to run the test program.
next reply other threads:[~2020-05-08 8:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 8:40 harald at gigawatt dot nl [this message] 2020-05-08 8:44 ` [Bug target/94998] " harald at gigawatt dot nl 2020-05-08 11:17 ` hjl.tools at gmail dot com 2020-05-08 11:28 ` [Bug bootstrap/94998] " rguenth at gcc dot gnu.org 2020-05-08 13:11 ` hjl.tools at gmail dot com 2020-05-08 17:02 ` harald at gigawatt dot nl 2020-05-12 17:42 ` cvs-commit at gcc dot gnu.org 2020-05-12 17:50 ` hjl.tools at gmail dot com 2020-06-22 8:50 ` slyfox at inbox dot ru 2020-06-22 8:55 ` rguenth at gcc dot gnu.org 2020-06-22 12:09 ` [Bug bootstrap/94998] [10 Regression] " cvs-commit at gcc dot gnu.org 2020-06-22 12:10 ` hjl.tools at gmail dot com
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-94998-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).