FS#71023 - makepkg for glibc does not work out of box

Attached to Project: Arch Linux
Opened by Makoto Mizukami (makotom) - Wednesday, 26 May 2021, 03:59 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 26 May 2021, 04:53 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Running makepkg against glibc does not work out of box, i.e., on a clean installation of Arch Linux.
This is mainly because `makepkg` changed its default compiler options recently, while glibc package has not facilitated it yet.

Additional info:
* package version(s): glibc-2.33-5 (source)

Steps to reproduce:

1. Set up a cleanly-installed Arch Linux environment.
Please note that you should use a clean environment with the default `makepkg.conf` to reproduce the issue.

2. Run makepkg against https://github.com/archlinux/svntogit-packages/tree/packages/glibc/trunk

Expected behaviour:

Build succeeds.

Actual behaviour:

GCC raises an error.

Analysis:

The reporter confirmed that the following patch fixes the issue, along with pacman-5.2.2.

https://github.com/makotom/glibc-wsl/blob/main/PKGBUILD-CFLAGS.patch

Indeed there was a recent change in the default compiler options for `makepkg`.

https://github.com/archlinux/svntogit-packages/blame/packages/pacman/trunk/makepkg.conf#L40-L44

Therefore `-D_FORTIFY_SOURCE=2` option remains for build of glibc, causing GCC to raise an error to embed inline functions, unless tuned correctly.

The reporter also sees a further change in those C flags, meaning that the patch aforementioned can be voided in the near future.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 26 May 2021, 04:53 GMT
Reason for closing:  Not a bug
Additional comments about closing:  PKGBUILDs in the repos are meant to be built in a clean chroot. devtools hasn't changed build options yet.

Loading...