Arch Linux User Repository

Currently the build fails (latest Arch state 2026-04-28, lib32-openssl-1.1 -> 1.1.1.w-5):

Test Summary Report
-------------------
../test/recipes/80-test_ca.t                     (Wstat: 256 (exited 1) Tests: 5 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
../test/recipes/90-test_includes.t               (Wstat: 1024 (exited 4) Tests: 5 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
../test/recipes/90-test_store.t                  (Wstat: 32000 (exited 125) Tests: 209 Failed: 125)
  Failed tests:  37-39, 41-43, 45-47, 49-51, 53-55, 57-59
                61-63, 65-67, 69-71, 73-75, 77-79, 81-83
                85-87, 89-91, 93-95, 97-99, 101-103, 105-107
                109-111, 113-115, 117-119, 121-123, 125-127
                129-131, 133-135, 137-139, 141-143, 145-147
                149-151, 153-155, 157-159, 161-163, 165-167
                169-171, 173-175, 177-179, 181-183, 185-187
                189-193, 204-209
  Non-zero exit status: 125
Files=160, Tests=2661, 132 wallclock secs ( 1.63 usr  0.19 sys + 122.01 cusr 18.44 csys = 142.27 CPU)
Result: FAIL
make[1]: *** [Makefile:208: _tests] Error 1
make[1]: Leaving directory '/home/jack/.cache/yay/lib32-openssl-1.1/src/openssl-1.1.1w'
make: *** [Makefile:205: tests] Error 2
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: lib32-openssl-1.1-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
lib32-openssl-1.1 - exit status 4

Clearing the yay build cache, has no effect. Has someone a clue/hint about it?

I think the lib crypto log in the first line is a red herring, it's probably just the lib crypto finishing properly building, not related to the errors coming next.

I suspect multilib-build installs multilib-devel in the chroot (EDIT: confirmed), as an equivalent to the base-devel package group implicitly required for aur packages. That's what must provide lib32-gcc-libs on your chroot. Just like base-devel, it's an (implicit) make depends, not a runtime dependency of the package.

I don't know the archlinux policy around this. I couldn't find multilib-devel mentioned in https://wiki.archlinux.org/title/Arch_User_Repository, so if it is indeed implicitly required for lib32 aur packages, it should probably be added there. There's currently very little mention of multilib-devel anywhere on the entire archlinux wiki.

But I think multilib-build is an artifact from the multilib repository, where different requirements than the aur might apply.

EDIT: Thanks for the fix!

@gyscos

Are you referring to the arch docker container as a clean chroot environment? Because, whenever I use the actual chroot tools on a real Arch Linux install (multilib-build -c -- -I /home/hurricane/aur/lib32-openssl-1.1/openssl-1.1/openssl-1.1-1.1.1.w-9-x86_64.pkg.tar.zst which makes a clean multilib chroot and installs openssl-1.1 into it), I can build lib32-openssl-1.1 from scratch.

Furthermore, whenever I check the package with namcap, I get:

lib32-openssl-1.1 W: Referenced library 'libcrypto.so.1.1' is an uninstalled dependency (needed in files ['usr/lib32/libssl.so.1.1', 'usr/lib32/openssl-1.1/engines-1.1/padlock.so', 'usr/lib32/openssl-1.1/engines-1.1/afalg.so'])

This just means that libcrypto.so.1.1, which is in the package, isn't installed yet. But most importantly, this means that the package doesn't even depend on lib32-gcc-libs. lib32-gcc-libs isn't even ever listed in makedepends(). If a package requires it, it's because its linking to it and thus will be in depends().

Since you are using an Arch Linux docker image, make sure you are updating the mirrors and the image with sudo pacman -Syu to get the latest version of Arch as described in the Docker Wiki Page.

TL;DR: I'm not going to add lib32-gcc-libs to makedepends() as it's not needed on actual Arch nor the official chroot tools. Plus, it wouldn't go there, it would go to depends() if the package actually needed it.

I am on a clean archlinux docker container.

The final few lines of the build logs include:

ar: creating libcrypto.a
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/../../../libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/../../../libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: cannot find libgcc_s.so.1: No such file or directory
/usr/bin/ld/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/../../../libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/../../../libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/../../../libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: cannot find libgcc_s.so.1: No such file or directory
collect2: error: ld returned 1 exit status
/usr/bin/ldmake[1]: *** [Makefile:8963: test/rsa_complex] Error 1
make[1]: *** Waiting for unfinished jobs....
: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/15.2.1/../../../libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
/usr/bin/ld: skipping incompatible /usr/lib/libgcc_s.so.1 when searching for libgcc_s.so.1
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:9041: test/shlibloadtest] Error 1
ranlib libcrypto.a || echo Never mind.
make[1]: Leaving directory '/build/src/lib32-openssl-1.1/src/openssl-1.1.1w'
make: *** [Makefile:174: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'lib32-openssl-1.1-1.1.1.w-4':
error: packages failed to build: lib32-openssl-1.1-1.1.1.w-4

This is an indicator of no 32-bit libgcc_s.so.1 being installed, which happens because lib32-gcc-libs is not installed.

Can you confirm lib32-gcc-libs is indeed not installed in your chroot? (tools like paru that can install in a chroot do not use a clean chroot, they re-use the same chroot over and over with plenty of dependencies from other packages being left there.)

Do you have any other libgcc_s.so.1 in /usr/lib32 in that chroot?

@gyscos

I am able to build this package in a clean CHROOT without lib32-gcc-libs as a makedepends(). Are you on Arch or an Arch derivative?

Hi!

Very similar to lib32-openssl-1.0, this package should list lib32-gcc-libs as a makedependency. Otherwise, it cannot be built in a clean chroot.