public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bero at lindev dot ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/96845] New: undefined reference to `__aarch64_ldadd4_acq_rel' Date: Sat, 29 Aug 2020 17:40:04 +0000 [thread overview] Message-ID: <bug-96845-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96845 Bug ID: 96845 Summary: undefined reference to `__aarch64_ldadd4_acq_rel' Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: bero at lindev dot ch Target Milestone: --- When compiling some packages on aarch64 (e.g. polkit-qt-1 0.113.0) on aarch64, the build errors out with /usr/lib64/gcc/aarch64-openmandriva-linux-gnu/10.2.0/../../../../aarch64-openmandriva-linux-gnu/bin/ld: core/CMakeFiles/polkit-qt5-core-1.dir/polkitqt1-authority.cpp.o: in function `std::__atomic_base<int>::operator++()': /usr/include/c++/10.2.0/bits/atomic_base.h:326: undefined reference to `__aarch64_ldadd4_acq_rel' This seems to be caused by __aarch64_ldadd4_acq_rel being defined in libgcc, but not libgcc_s, while only libgcc_s is pulled in automatically. Some Linux distributions have a workaround for this in their gcc packaging - they replace libgcc_s.so with an ld script that pulls in libgcc if needed (see e.g. https://src.fedoraproject.org/rpms/gcc/blob/master/f/gcc.spec#_1303 )
next reply other threads:[~2020-08-29 17:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-29 17:40 bero at lindev dot ch [this message] 2020-08-29 18:19 ` [Bug libgcc/96845] " pinskia at gcc dot gnu.org 2020-08-29 18:20 ` 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-96845-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).