public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libgcc/96845] New: undefined reference to `__aarch64_ldadd4_acq_rel'
@ 2020-08-29 17:40 bero at lindev dot ch
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
0 siblings, 2 replies; 3+ messages in thread
From: bero at lindev dot ch @ 2020-08-29 17:40 UTC (permalink / raw)
To: gcc-bugs
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 )
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libgcc/96845] undefined reference to `__aarch64_ldadd4_acq_rel'
2020-08-29 17:40 [Bug libgcc/96845] New: undefined reference to `__aarch64_ldadd4_acq_rel' bero at lindev dot ch
@ 2020-08-29 18:19 ` pinskia at gcc dot gnu.org
2020-08-29 18:20 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2020-08-29 18:19 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96845
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is a distro issue.
libgcc_s.so is a linker script when compiling GCC by itself.
It contains:
/* GNU ld script
Use the shared library, but some functions are only in
the static library. */
GROUP ( libgcc_s.so.1 -lgcc )
---- CUT ----
SO again this is a distro issue.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libgcc/96845] undefined reference to `__aarch64_ldadd4_acq_rel'
2020-08-29 17:40 [Bug libgcc/96845] New: undefined reference to `__aarch64_ldadd4_acq_rel' bero at lindev dot ch
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
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2020-08-29 18:20 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96845
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Bernhard Rosenkraenzer from comment #0)
> 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
Or rather they replace the already ld script with another ld script ...
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-08-29 18:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-08-29 17:40 [Bug libgcc/96845] New: undefined reference to `__aarch64_ldadd4_acq_rel' bero at lindev dot ch
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
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).