public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/29455] [gdb/build, clang-13] undefined reference to `__atomic_load' Date: Tue, 09 Aug 2022 08:46:21 +0000 [thread overview] Message-ID: <bug-29455-4717-i9EnfN3735@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29455-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29455 --- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> --- (In reply to Tom de Vries from comment #5) > I also tried building on openSUSE tumbleweed, with clang 14.0.6, where clang > also selects gcc-12, but in this case it's the system gcc. > > Same problem occurs. > I managed to complete a build using: ... diff --git a/gdb/Makefile.in b/gdb/Makefile.in index 2598b81d205..ebd7d27dc11 100644 --- a/gdb/Makefile.in +++ b/gdb/Makefile.in @@ -654,7 +654,7 @@ CLIBS = $(SIM) $(READLINE) $(OPCODES) $(LIBCTF) $(BFD) $(ZLIB ) \ $(LIBEXPAT) $(LIBLZMA) $(LIBBABELTRACE) $(LIBIPT) \ $(WIN32LIBS) $(LIBGNU) $(LIBGNU_EXTRA_LIBS) $(LIBICONV) \ $(LIBMPFR) $(LIBGMP) $(SRCHIGH_LIBS) $(LIBXXHASH) $(PTHREAD_LIBS) \ - $(DEBUGINFOD_LIBS) $(LIBBABELTRACE_LIB) + $(DEBUGINFOD_LIBS) $(LIBBABELTRACE_LIB) -latomic CDEPS = $(NAT_CDEPS) $(SIM) $(BFD) $(READLINE_DEPS) $(CTF_DEPS) \ $(OPCODES) $(INTL_DEPS) $(LIBIBERTY) $(CONFIG_DEPS) $(LIBGNU) \ $(LIBSUPPORT) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-09 8:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-08 8:09 [Bug build/29455] New: " vries at gcc dot gnu.org 2022-08-08 8:40 ` [Bug build/29455] " vries at gcc dot gnu.org 2022-08-08 9:01 ` vries at gcc dot gnu.org 2022-08-08 13:43 ` tromey at sourceware dot org 2022-08-08 15:09 ` vries at gcc dot gnu.org 2022-08-09 8:33 ` vries at gcc dot gnu.org 2022-08-09 8:46 ` vries at gcc dot gnu.org [this message] 2022-08-12 3:15 ` lienze at sourceware dot 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-29455-4717-i9EnfN3735@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).