Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#73147 - [aarch64-linux-gnu-gcc] Inconsistent libdir naming between gcc and glibc

Attached to Project: Community Packages
Opened by Sergey Kvachonok (ravenexp) - Saturday, 25 December 2021, 12:14 GMT
Last edited by Morten Linderud (Foxboron) - Tuesday, 28 December 2021, 12:12 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Anatol Pomozov (anatolik)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

aarch64-linux-gnu-gcc installs its libraries to '/usr/aarch64-linux-gnu/lib64/'.
aarch64-linux-gnu-glibc installs its libraries to '/usr/aarch64-linux-gnu/lib/'.

Additional info:
* aarch64-linux-gnu-gcc-11.2.0-1
* aarch64-linux-gnu-glibc-2.34-1

Steps to reproduce:

Currently, it's impossible to set LD_LIBRARY_PATH to a directory where both "libgcc_s.so.1" and "libc.so.6" are present.
This makes using e.g. qemu-aarch64 a major pain.

Expected behavior:

aarch64-linux-gnu-gcc installs its libraries to '/usr/aarch64-linux-gnu/lib/' just like glibc does.
This task depends upon

Loading...