| Git Clone URL: | https://aur.archlinux.org/lib32-lzo.git (read-only, click to copy) |
|---|---|
| Package Base: | lib32-lzo |
| Description: | Portable lossless data compression library (32 bit) |
| Upstream URL: | https://www.oberhumer.com/opensource/lzo/ |
| Licenses: | GPL |
| Submitter: | rafaelff |
| Maintainer: | dbermond |
| Last Packager: | dbermond |
| Votes: | 41 |
| Popularity: | 0.084293 |
| First Submitted: | 2014-07-31 18:15 (UTC) |
| Last Updated: | 2018-12-03 16:09 (UTC) |
Notice:
The multilib-devel package is required to be installed to build multilib (lib32-*) packages, in the same way that base-devel is required to build non-multilib packages. Also, the multilib repository needs to be enabled in pacman. At the time of writing, the package is building fine with makepkg and also in a clean chroot.
If building in a clean chroot, I highly recommend using multilib-build tool from devtools because other tools (makechrootpkg, extra-build, etc.) do not have the multilib-devel meta-package nor have the multilib repository enabled by default.
lib32-lzo does not build in a clean chroot. (A clean chroot is the recommended environment for official Arch packages to be built in: it consists of the base and base-devel packages, as well as the package's dependencies and makedependencies.) All 32-bit packages that I've ever built require lib32-gcc-libs, and lib32-lzo does not specify this dependency. Here is the output:
...
==> Making package: lib32-lzo 2.10-2 (Sun Apr 23 16:12:24 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
configure: Configuring LZO 2.10
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc -m32
checking whether the C compiler works... no
configure: error: in `/build/lib32-lzo/src/lzo-2.10':
configure: error: C compiler cannot create executables
See `config.log' for more details
Adding lib32-gcc-libs allows the package to be built correctly, and one could remove lib32-glibc as lib32-gcc-libs pulls it in.
Thanks for your work on this package!
@bda I've just checked, and the package is building fine for me. Make sure that you have the multilib-devel package installed and try to build in a clean chroot.
Error when compiling with rua
==> Making package: lib32-lzo 2.10-2 (Tue Feb 28 15:20:15 2023)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading lzo-2.10.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 586k 100 586k 0 0 1075k 0 --:--:-- --:--:-- --:--:-- 1076k
==> Validating source files with sha256sums...
lzo-2.10.tar.gz ... Passed
==> Extracting sources...
-> Extracting lzo-2.10.tar.gz with bsdtar
==> Starting build()...
configure: Configuring LZO 2.10
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc -m32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... configure: error: in `/home/bruno/.cache/rua/build/lib32-lzo/src/lzo-2.10':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
==> ERROR: A failure occurred in build().
Aborting...
Build failed with exit code 4 in /home/bruno/.cache/rua/build/lib32-lzo
config.log:
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.1 20230201 (GCC)
configure:3131: $? = 0
configure:3120: gcc -m32 -V >&5
gcc: error: unrecognized command-line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:3131: $? = 1
configure:3120: gcc -m32 -qversion >&5
gcc: error: unrecognized command-line option '-qversion'; did you mean '--version'?
gcc: fatal error: no input files
compilation terminated.
configure:3131: $? = 1
configure:3151: checking whether the C compiler works
configure:3173: gcc -m32 -march=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.c >&5
configure:3177: $? = 0
configure:3225: result: yes
configure:3228: checking for C compiler default output file name
configure:3230: result: a.out
configure:3236: checking for suffix of executables
configure:3243: gcc -m32 -o conftest -march=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.c >&5
configure:3247: $? = 0
configure:3269: result:
configure:3291: checking whether we are cross compiling
configure:3299: gcc -m32 -o conftest -march=native -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.c >&5
configure:3303: $? = 0
configure:3310: ./conftest
./configure: line 3312: 939 Bad system call (core dumped) ./conftest$ac_cv_exeext
configure:3314: $? = 159
configure:3321: error: in `/home/bruno/.cache/rua/build/lib32-lzo/src/lzo-2.10':
configure:3323: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
@dr460nf1r3 This is not needed, since lib32-gcc-libs is on the multilib-devel group. This group is also required when building multilib packages.
Please add lib32-gcc-libs to makedepends.
Pinned Comments
dbermond commented on 2023-06-20 00:53 (UTC)
Notice:
The multilib-devel package is required to be installed to build multilib (lib32-*) packages, in the same way that base-devel is required to build non-multilib packages. Also, the multilib repository needs to be enabled in pacman. At the time of writing, the package is building fine with makepkg and also in a clean chroot.