public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/107552] New: [13 regression] stage 1 d21 fails to link on Linux/x86_64 Date: Mon, 07 Nov 2022 13:01:07 +0000 [thread overview] Message-ID: <bug-107552-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107552 Bug ID: 107552 Summary: [13 regression] stage 1 d21 fails to link on Linux/x86_64 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: d Assignee: ibuclaw at gdcproject dot org Reporter: ro at gcc dot gnu.org Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Build: x86_64-pc-linux-gnu I've long been bootstrapping trunk with GCC 9.3.0. However, between 20221028 (11e811d8e2f63667f60f73731bb934273f5882b8) and 20221104 (e724b0480bfa5ec04f39be8c7290330b495c59de), bootstrap broke linking stage 1 d21: /vol/gcc/bin/gld-2.35: d/typesem.o:(.data+0x180): multiple definition of `___s.24340'; d/statementsem.o:(.data+0x260): first defined here collect2: error: ld returned 1 exit status make: *** [/vol/gcc/src/hg/master/local/gcc/d/Make-lang.in:234: d21] Error 1 I've tried with GCC 11.1.0: while the stage 1 d21 links this way, the resulting gdc/d21 fails to run because d21 is linked with libstdc++ dynamically, using a version that's newer than the one bundled with Ubuntu 20.04. Passing through LD_LIBRARY_PATH is tricky and does cause a couple of testsuite regressions. GCC 12.1.0 does work, and stage 1 d21 is linked statically with libstd++, as expected. However, this means quite massive an increase in build requirements.
next reply other threads:[~2022-11-07 13:01 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-07 13:01 ro at gcc dot gnu.org [this message] 2022-11-07 14:14 ` [Bug d/107552] " ibuclaw at gdcproject dot org 2022-11-08 8:17 ` ro 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-107552-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).