You are not logged in.
I tend to build all my packages for my system's specific architecture (znver2), and while this is still doable and the package names *can* be adjusted to reflect that by adjusting CARCH in makepkg.conf, makechrootpkg does not respect this.
I would have reported such as a bug to the associated gitlab page, but the login portal there for new users is bugged and won't accept my 2FA tokens provided via KeePassXC :/
Not sure who to talk to about this exactly, so I figured I'd put this info out there.
Offline
... by adjusting CARCH in makepkg.conf, makechrootpkg does not respect this.
Which makepkg.conf are you adjusting? The one in the chroot, or the one for the host system? And / or how did you create the chroot (did you use the -M flag passing your makepkg.conf *after* you had edited CARCH?
Last edited by Trilby (2022-06-25 17:52:52)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I've done it for both
Offline
I find it baffling that I couldn't just easily register for the Gitlab and reported it without issue though...
There isn't even a support email for it
Offline
Gitlab transition is afaik still WIP and not open to the public, do your bug reports/feature requests on https://bugs.archlinux.org/
Offline
@V1del Thanks for letting me know
Offline
Offline
You probably don't want a different architecture anyway. Unless you are distributing to other people. Adjust the devtools makepkg.conf CFLAGS to use -march=native.
Offline