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!
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!
FS#68489 - [aarch64-linux-gnu-gcc] Align with gcc
Attached to Project:
Community Packages
Opened by Christer Solskogen (solskogen) - Sunday, 01 November 2020, 07:41 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 30 March 2021, 11:42 GMT
Opened by Christer Solskogen (solskogen) - Sunday, 01 November 2020, 07:41 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 30 March 2021, 11:42 GMT
|
Detailsgcc is configured with --enable-default-pie, while aarch64-linux-gnu-gcc is not.
This breaks cross compiling with distcc is some cases. |
This task depends upon
Do all *-linux-gnu-gcc packages need to be aligned? for example riscv64-linux-gnu-gcc neither has this flag.
(native) gcc for Arch Linux *is* compiled with --enable-default-pie. It's just that the aarch64 cross compiler isn't. The same goes for the native gcc on Arch Linux ARM.
The missing --enable-default-pie is the only GCC configure flag that I know causes linker problems, as I've edited the PKGBUILD for aarch64-linux-gnu-gcc myself with that flag added and haven't seen any other issues.
I can't say for sure about other archs, since I haven't tested them.
The change got merged to SVN and it will be available with the next package rebuild (10.2.1).