public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/101377] [11/12 Regression] 'exec format error' on x86_64-w64-mingw32 Date: Thu, 08 Jul 2021 13:58:43 +0000 [thread overview] Message-ID: <bug-101377-4-NBG7miA0tT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101377-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101377 --- Comment #4 from Liu Hao <lh_mouse at 126 dot com> --- configure said 'yes' for 'broken dwarf5 support'. I am not quite clear whether this means whether it is broken or not (but I suspect yes): ``` configure:29798: checking linker PT_GNU_EH_FRAME support configure:29829: result: no configure:29832: checking linker CIEv3 in .eh_frame support configure:29869: result: yes configure:29872: checking linker position independent executable support configure:29913: result: yes configure:29916: checking linker PIE support with copy reloc configure:29965: result: no configure:29968: checking linker EH-compatible garbage collection of sections configure:30048: result: no configure:30051: checking linker EH garbage collection of sections bug configure:30095: result: no configure:30098: checking linker for compressed debug sections configure:30158: result: 3 configure:30228: checking broken PE linker dwarf5 support configure:30249: result: yes configure:30258: checking linker --as-needed support configure:30319: result: yes ``` This macro was also defined: ``` | #define HAVE_LD_BROKEN_PE_DWARF5 1 ```
next prev parent reply other threads:[~2021-07-08 13:58 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-08 11:32 [Bug bootstrap/101377] New: " lh_mouse at 126 dot com 2021-07-08 12:10 ` [Bug bootstrap/101377] [11/12 Regression] " rguenth at gcc dot gnu.org 2021-07-08 12:11 ` rguenth at gcc dot gnu.org 2021-07-08 12:37 ` ebotcazou at gcc dot gnu.org 2021-07-08 13:58 ` lh_mouse at 126 dot com [this message] 2021-07-08 14:50 ` ebotcazou at gcc dot gnu.org 2021-07-08 14:54 ` lh_mouse at 126 dot com 2021-07-08 15:34 ` ebotcazou at gcc dot gnu.org 2021-07-08 15:42 ` lh_mouse at 126 dot com 2021-07-08 16:09 ` ebotcazou at gcc dot gnu.org 2021-07-08 16:09 ` ebotcazou at gcc dot gnu.org 2021-07-08 16:35 ` ebotcazou at gcc dot gnu.org 2021-07-08 16:55 ` [Bug target/101377] " lh_mouse at 126 dot com 2021-07-08 17:24 ` ebotcazou at gcc dot gnu.org 2021-07-08 17:46 ` pinskia at gcc dot gnu.org 2021-07-09 3:46 ` lh_mouse at 126 dot com 2021-07-09 10:14 ` cvs-commit at gcc dot gnu.org 2021-07-09 10:14 ` cvs-commit at gcc dot gnu.org 2021-07-09 10:15 ` ebotcazou at gcc dot gnu.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-101377-4-NBG7miA0tT@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).