public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnewtonrichards at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/109698] gcc/g++ build/link fails for libhwasan.so
Date: Fri, 12 May 2023 17:16:03 +0000 [thread overview]
Message-ID: <bug-109698-4-BjRErbhYXB@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 #5 from David Richards <dnewtonrichards at gmail dot com> ---
To add a bit more (not much - just a tad). I was able to build gcc/g++
version 12.3.0 just recently released without any problems.
Then I attempted to build 13.1 with 12.3 and still no luck. Same error...
On Tue, May 2, 2023 at 10:42 AM <gcc-bugzilla@gcc.gnu.org> wrote:
> Attachments with a MIME type of "text/html" are not allowed on this
> installation.
>
> David Richards wrote:
> > ld --version:
> > GNU ld (GNU Binutils for Debian) 2.31.1
> > Copyright (C) 2018 Free Software Foundation, Inc.
> > This program is free software; you may redistribute it under the terms of
> > the GNU General Public License version 3 or (at your option) a later
> > version.
> > This program has absolutely no warranty.
> > NOTE: I have built gcc/g++ version 12.2 o0n this same system
> > Thanks!
> > Dave
> >
> > On Tue, May 2, 2023 at 9:18 AM jakub at gcc dot gnu.org <
> > gcc-bugzilla@gcc.gnu.org> wrote:
> >
> > > 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?
> > >
> > > --
> > > You are receiving this mail because:
> > > You reported the bug.
>
next prev parent reply other threads:[~2023-05-12 17:16 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
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 [this message]
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-BjRErbhYXB@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).