Bug 1830472 - undefined reference to `__aarch64_ldadd4_acq_rel
Summary: undefined reference to `__aarch64_ldadd4_acq_rel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2020-05-02 04:29 UTC by Mattias Ellert
Modified: 2022-09-13 09:39 UTC (History)
18 users (show)

Fixed In Version: gcc-10.0.1-0.14.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-07 03:10:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mattias Ellert 2020-05-02 04:29:47 UTC
Description of problem:

After gcc was updated to version 10.0.1-0.13 the build of root started failing in koschei for aarch64 with a missing symbol during linking:
https://koschei.fedoraproject.org/package/root?collection=f33

Version-Release number of selected component (if applicable):

gcc-c++-10.0.1-0.13.fc33.aarch64

How reproducible:

I triggered a second attempt in koschei and it failed the same way.

Steps to Reproduce:
1. Build root in rawhide

Actual results:

Build fails with missing symbol

Expected results:

Successful build

Additional info:

/usr/bin/ld: /usr/include/c++/10/ext/atomicity.h:50: undefined reference to `__aarch64_ldadd4_acq_rel'

Comment 1 Jakub Jelinek 2020-05-02 11:45:59 UTC
On aarch64 -moutline-atomics has been turned on by default, and those symbols are solely in libgcc.a, not in libgcc_s.so.*.
So, libgcc_s.so linker script is needed instead of libgcc_s.so symlink like on some other arches, gcc-10.0.1-0.14.fc33 with a fix is building in koji.

Comment 2 Jakub Jelinek 2020-05-03 09:08:19 UTC
Should be hopefully fixed in gcc-10.0.1-0.14.fc33.

Comment 3 Elliott Sales de Andrade 2020-05-04 05:33:03 UTC
This is also currently a problem on Fedora 32: https://koji.fedoraproject.org/koji/taskinfo?taskID=44074576 and there do not appear to be any new builds.

Comment 4 Jakub Jelinek 2020-05-04 07:05:02 UTC
Yes, because the F32 build wasn't intended to be pushed, I built it in F32 too just because some people wanted it.

Comment 5 Mattias Ellert 2020-05-05 04:39:40 UTC
Now also affects Fedora 32 with gcc-10.0.1-0.13.fc32, see e.g.:

https://koschei.fedoraproject.org/package/xrootd?collection=f32

Hovever, rawhide is no longer affected with gcc-10.0.1-0.14.fc33. see e.g.

https://koschei.fedoraproject.org/package/xrootd?collection=f33

Comment 6 Miro Hrončok 2020-05-05 17:35:57 UTC
Please, can we get the broken build untagged from Fedora 32? This is blocking other packages.

Comment 8 Fedora Update System 2020-05-05 18:23:47 UTC
FEDORA-2020-c66e53d090 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c66e53d090

Comment 9 Fedora Update System 2020-05-06 02:23:31 UTC
FEDORA-2020-c66e53d090 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c66e53d090`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c66e53d090

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2020-05-07 03:10:07 UTC
FEDORA-2020-c66e53d090 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 sxs 2022-09-13 09:34:18 UTC
How can resolve this issue? my gcc version is 7.5.0

Comment 12 Florian Weimer 2022-09-13 09:39:11 UTC
(In reply to sxs from comment #11)
> How can resolve this issue? my gcc version is 7.5.0

You need to talk to the party who supplied your compiler, or the libraries you use. I do not think any GCC 7 versions are still under support by Red Hat.


Note You need to log in before you can comment on or make changes to this bug.