public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/109698] gcc/g++ build/link fails for libhwasan.so Date: Tue, 02 May 2023 13:18:09 +0000 [thread overview] Message-ID: <bug-109698-4-7cnrQ5n8vJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109698-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109698 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Seems binutils has added support for __ehdr_start only in https://sourceware.org/legacy-ml/binutils/2012-06/msg00171.html in 2012. Do you have binutils older than that?
next prev parent reply other threads:[~2023-05-02 13:18 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-02 13:00 [Bug c++/109698] New: " dnewtonrichards at gmail dot com 2023-05-02 13:12 ` [Bug sanitizer/109698] " pinskia at gcc dot gnu.org 2023-05-02 13:18 ` jakub at gcc dot gnu.org [this message] 2023-05-02 14:40 ` dnewtonrichards at gmail dot com 2023-05-02 14:42 ` dnewtonrichards at gmail dot com 2023-05-12 17:16 ` dnewtonrichards at gmail dot com 2023-08-29 6:37 ` zeratul976 at hotmail dot com 2023-08-29 6:45 ` zeratul976 at hotmail dot com 2023-08-29 6:50 ` pinskia 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-109698-4-7cnrQ5n8vJ@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).