Arch Linux User Repository

Hi, yes it builds and works, thank you. After I posted the error here, I spent like 2 hours prompting LLMs to try to solve the issue, they weren't even close to this or any solution. :D

I have constrained the libsoup build configuration to match the one on a clean chroot. It should build now, unless something else also needs to be explicitly configured.

objcopy: ./x86_64-linux-gnu/girepository-1.0/Soup-3.0.typelib: file format not recognized

I am not sure what is causing this but my first thought is that it's some other package present in the system, that the build process picks up. It's not happening here when building in a clean chroot (paru can automate that if needed). Sadly I don't know which package that is presently.

I'm getting this error when trying to build it, had no issues with version 10

Installing /ssd2/csaba/.cache/yay/proton-cachyos/src/build/obj-libsoup-x86_64/meson-private/libsoup-3.0.deps to /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/share/vala/vapi
Installing symlink pointing to libsoup-3.0.so.0.7.4 to /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib/x86_64-linux-gnu/libsoup-3.0.so.0
Installing symlink pointing to libsoup-3.0.so.0 to /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib/x86_64-linux-gnu/libsoup-3.0.so
touch /ssd2/csaba/.cache/yay/proton-cachyos/src/build/.libsoup-x86_64-build
touch /ssd2/csaba/.cache/yay/proton-cachyos/src/build/.libsoup-x86_64-post-build
:: installing libsoup-x86_64...
if [ -f "/ssd2/csaba/.cache/yay/proton-cachyos/src/build/obj-libsoup-x86_64/compile_commands.json" ]; then mkdir -p "/ssd2/csaba/.cache/yay/proton-cachyos/src/build/compile_commands/libsoup-x86_64/"; sed "s#/ssd2/csaba/.cache/yay/proton-cachyos/src/build/src-libsoup#/ssd2/csaba/.cache/yay/proton-cachyos/src/proton-cachyos/libsoup#g" "/ssd2/csaba/.cache/yay/proton-cachyos/src/build/obj-libsoup-x86_64/compile_commands.json" > "/ssd2/csaba/.cache/yay/proton-cachyos/src/build/compile_commands/libsoup-x86_64/compile_commands.json"; fi
mkdir -p /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib/ /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/
cd /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib && find -type f -printf '/ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/%h\0' | sort -z | uniq -z | xargs --verbose -0 -r -P1 mkdir -p
mkdir -p /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/girepository-1.0 /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/pkgconfig
cd /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib && find -type l -printf '%p\0/ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/%p\0' | xargs --verbose -0 -r -P1 -n2 cp -a
cp -a ./x86_64-linux-gnu/libsoup-3.0.so.0 /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/libsoup-3.0.so.0
cp -a ./x86_64-linux-gnu/libsoup-3.0.so /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/libsoup-3.0.so
cd /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib && find -type f -not '(' -iname '*.pc' -or -iname '*.cmake' -or -iname '*.a' -or -iname '*.la' -or -iname '*.def' -or -iname '*.h' ')' -printf '/ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/%p.debug\0' | xargs --verbose -0 -r -P1 rm -f
rm -f /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/libsoup-3.0.so.0.7.4.debug /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/girepository-1.0/Soup-3.0.typelib.debug
cd /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dst-libsoup-x86_64/lib && find -type f -not '(' -iname '*.pc' -or -iname '*.cmake' -or -iname '*.a' -or -iname '*.la' -or -iname '*.def' -or -iname '*.h' ')' -printf '--strip-debug\0%p\0/ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/%p\0' | xargs --verbose -0 -r -P1 -n3 objcopy -p --set-section-flags .text=contents,alloc,load,readonly,code
objcopy -p --set-section-flags '.text=contents,alloc,load,readonly,code' --strip-debug ./x86_64-linux-gnu/libsoup-3.0.so.0.7.4 /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/libsoup-3.0.so.0.7.4
objcopy -p --set-section-flags '.text=contents,alloc,load,readonly,code' --strip-debug ./x86_64-linux-gnu/girepository-1.0/Soup-3.0.typelib /ssd2/csaba/.cache/yay/proton-cachyos/src/build/dist/files/lib/./x86_64-linux-gnu/girepository-1.0/Soup-3.0.typelib
objcopy: ./x86_64-linux-gnu/girepository-1.0/Soup-3.0.typelib: file format not recognized
make[1]: *** [../proton-cachyos/Makefile.in:315: /ssd2/csaba/.cache/yay/proton-cachyos/src/build/.libsoup-x86_64-dist] Error 123
make[1]: Leaving directory '/ssd2/csaba/.cache/yay/proton-cachyos/src/build'
make: *** [../proton-cachyos/Makefile.in:2496: dist] Error 2
==> ERROR: A failure occurred in build().

@loathingkernel @ptr1337 Huge appreciation to you and the team. As an IT worker who builds often but is still "learning" Arch (even after nearly a decade), I want to acknowledge the massive effort and hardware stress that goes into maintaining this. You're appreciated.

I saw the recent comments - ignore the noise. Some people don't understand "bleeding edge" means occasionally getting cut.

I’ve spent the last hour diving into makepkg.conf to optimize my environment (3900X/128GB RAM). Moving the build to a 64G tmpfs and cranking the MAKEFLAGS to -j22. I’m also testing ccache despite the PKGBUILD's specific wrappers, just to see if I can shorten that 30-minute re-run. And I've never done that for a package (usually just look for a -bin). So thanks to your efforts I've levelled up.

Thanks for providing the community with these tools.

Edit:

Switching the build to memory instead of nvme cut the time down from ~30m to ~10m. In my case,

ModuleNotFoundError: No module named 'fontTools' make[1]: *** [../proton-cachyos/Makefile.in:2028: obj-fonts/micross.ttf] Error 1".

Installing as user python -m pip install fonttools was all I needed. Cheers.

had an issue for rustup target i686-unknown-linux-gnu so I modified the PKGBUILD slightly to fix it.

--- ./ORIG_PKGBUILD  2026-03-27 19:15:53.140338342 -0600
+++ ./MOD_PKGBUILD  2026-03-27 19:15:13.247863979 -0600
@@ -264,7 +264,9 @@
         export CARGO_HOME="${SRCDEST}"/proton-cargo
         export CARGO_NET_GIT_FETCH_WITH_CLI=true
         cargo update
+        rustup target add i686-unknown-linux-gnu
         cargo fetch --locked --target i686-unknown-linux-gnu
+        rustup target add x86_64-unknown-linux-gnu
         cargo fetch --locked --target x86_64-unknown-linux-gnu
     popd
     done

@loathingkernel I just wanted to thank you - you maid my life easier.

@solx123 AUR is a repository for whatever packages nice people care to share (vs keeping to themselves) after spending time to build those packages. There is no guarantee it will work or even updated. A constructive approach when something is broken is: * optional - Try to understand why (dump the output to gpt/gemini) * optional - Try to fix it (ask gpt/gemini) - sometimes editing the pkgbuild is enough (for example dependencies). * Share the issue and the result of the "optional" steps above.

@solx123 If you spent 2 seconds reading the pkgbuid you would understand that you're compiling this. You can't just say I demand this to be deleted because you can't read smh.

Last thing you need is loathing loathing other things.

okay i apologize for that it was not exactly my intention to attack you or the work

@solx123 It didn't build successfully because of changes in other packages that happened after the previous update, at the time it was building successfully

proof:

previous: https://github.com/loathingKernel/PKGBUILDs/actions/runs/21805661501

current: https://github.com/loathingKernel/PKGBUILDs/actions/runs/22554714940

just mention in description that this package exists to waste the time of those who try to build it

So far the only waste of time I see here is interacting with you. If you do not understand that you are building proton from source, which contains a large amount of other projects, that's on you. You are the one telling your computer what to do, you choose what you build, if that's not what you expect, the only person you can blame is yourself.

but the main issue was that the build failed after running for nearly half an hour

Then you should probably have led with that, instead of attacking the usefulness of the package itself.