You are not logged in.

#1 2022-09-29 08:42:36

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,512

[Solved] which makepkg.conf to use for clean chroot building ?

The reports about mesa in testing failing with lto build made me wonder how lto could be enabled by default.

/etc/makepkg.conf comes from pacman package and was created by archlinux devs, see https://github.com/archlinux/svntogit-p … kepkg.conf
it has

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug !lto)


The tool used to build in clean chroots by devs & TUs is devtools and uses upstream files .

Looking at /usr/share/devtools there are 2 makepkg conf files, makepkg-x86_64.conf & makepkg-x86_64_v3.conf

both files have

OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)

pacman disables  lto by default and let's software decide if it should be used, devtools enables it by default.

Building in a clean chroot is often mentioned as a good method to verify AUR PKGBUILDs .

I have used extra-x86-build & multilib-build often, but am now wondering if it would be better to switch to https://wiki.archlinux.org/title/Develo … acman.conf and use the default makepkg.conf as it comes with pacman .

Last edited by Lone_Wolf (2022-09-30 09:29:20)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#2 2022-09-29 11:54:31

WorMzy
Forum Moderator
From: Scotland
Registered: 2010-06-16
Posts: 10,943
Website

Re: [Solved] which makepkg.conf to use for clean chroot building ?

LTO should be enabled by default now: https://gitlab.archlinux.org/archlinux/ … requests/4 https://gitlab.archlinux.org/archlinux/ … f86f0b0222

The options line in pacman's makepkg.conf hasn't been updated in 17 months: https://github.com/archlinux/svntogit-p … g.conf#L95, but I'm not sure if that's an oversight. I always build in clean chroots, so if LTO causes build failures for an AUR package I maintain, I'd add !lto at the PKGBUILD level.


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2022-09-30 09:28:54

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,512

Re: [Solved] which makepkg.conf to use for clean chroot building ?

I checked and found most of the aur packages I use have their own setting to enable / disable lto builds.
f.e. mesa trunk uses b_lto which defaults to false and makepkg lto flag setting doesn't make a difference.

I've changed my default in /etc/makepkg.conf to lto and am /usr/share/devtools/makepkg-x86_64.conf for clean chroot building.

I always build in clean chroots, so if LTO causes build failures for an AUR package I maintain, I'd add !lto at the PKGBUILD level.

I can't remember a single LTO issue that lead to build failure, but lots that caused runtime problems .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB