Hi, On Fri, Jun 26, 2026 at 12:47 AM <[email protected]> wrote: > > oech3 [1] filed a deletion request for gcc-fast-optimized [2]: > > -O3 and local cpu tuning should be part of your makepkg.conf .
For ordinary packages yes, but if you look at the source of gcc's PKGBUILD you'll quickly understand why this is not the case of archlinux's gcc package. It HAS to override some local flags due to how a complex build like gcc works. For instance, you cannot pass `-O3` to stage1 or you'll end up with a broken compiler. Afaik, makepkg.conf doesn't support the kind of granularity a build of gcc requires, but if I'm wrong lmk cause I'll certainly appreciate to not have a PKGBUILD to maintain :D > AUR cannot host -optimized for all packages pn AUR. It's not as if I was submitting `coreutils-fast-optimized` or `make-fast-opitimized`, gcc has completely different requirements, needs control over stage build flags. Also, with a good look at the PKGBUILD you will notice that it uses different build commands, not only a simple `-O3` CFLAGS that you could tune at makepkg.conf. It passes different config flags to autoconf and includes some extra config fragments to make. I mean, I would completely understand the policy if I was doing it to any ordinary package, but in that cases it completely misses the point. Unless makepkg adds support for such a custom build and the official package implements it. > > [1] https://aur.archlinux.org/account/oech3/ > [2] https://aur.archlinux.org/pkgbase/gcc-fast-optimized/
