Package Details: lib32-sratom 0.6.6-1

Git Clone URL: https://aur.archlinux.org/lib32-sratom.git (read-only, click to copy)
Package Base: lib32-sratom
Description: An LV2 Atom RDF serialisation library (32-bit)
Upstream URL: https://drobilla.net/software/sratom/
Licenses: custom:ISC
Submitter: rodrigo21
Maintainer: rodrigo21
Last Packager: rodrigo21
Votes: 1
Popularity: 0.000001
First Submitted: 2018-08-19 03:04
Last Updated: 2020-11-22 17:32

Latest Comments

DDoSolitary commented on 2020-08-23 07:41

I had the same problem as @programegg and fixed it by removing -fno-plt from CFLAGS in /etc/makepkg.conf and build lib32-sord again. It seems that the combination of -fno-plt and -O2 causes this problem. Removing either of them will work.

programegg commented on 2020-07-04 03:32

@rodrigo21 that's what I've been doing as a workaround.

However, I think I just figured out part of the trouble. This package runs the tests fine if lib32-sord was built using older gcc-9.3.0.1,gcc-libs-9.3.0.1,lib32-gcc-libs-9.3.0.1,glibc-2.31-1 and lib32-glibc-2.31-1 packages in a clean chroot. I didn't test other versions of gcc/glibc

rodrigo21 commented on 2020-06-11 01:30

@programegg You can disable the check() function in the PKGBUILD as it's falling the tests.

But I don't know if this will be a problem.

programegg commented on 2020-06-11 01:01

@rodrigo21 I'm having trouble building even in a clean chroot with multilib-build.

==> Starting check()...
Waf: Entering directory `/build/lib32-sratom/src/sratom-0.6.4/build'

[==========] Running sratom tests [ FAILED ] ./sratom_test [----------] 0/1 tests from sratom.Integration (310 ms total) [==========] 1 tests from sratom ran (439 ms total) Failed to run lcov to generate coverage report [ PASSED ] 0 tests [ FAILED ] 1 tests

Waf: Leaving directory `/build/lib32-sratom/src/sratom-0.6.4/build' ==> ERROR: A failure occurred in check(). Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/multilib-x86_64/user/build

If I don't use a clean chroot it also fails in the same manner. In my system journals I can see that I have a coredump at the time of the build related to sord_free with the following message:

                    Stack trace of thread 22247:
                               #0  0x00000000f7e385ca sord_free (libsord-0.so.0 + 0x45ca)
                               #1  0x000000005664cbdf n/a (/tmp/makepkg/lib32-sratom/src/sratom-0.6.4/build/sratom_test + 0xabdf)

rodrigo21 commented on 2020-06-08 14:42

@tt102 It's building for me in a clean chroot.

Check https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_clean_chroot and use multilib-build to build the package.

You will have to build lib32-lv, lib32-sord and lib32-serd and install the packages in the chroot.

tt102 commented on 2020-06-08 13:28

[8/8] Symlinking build/libsratom-0.so
Waf: Leaving directory /home/tyler/.cache/yay/lib32-sratom/src/sratom-0.6.4/build' 'build' finished successfully (0.671s) ==> Starting check()... Waf: Entering directory/home/tyler/.cache/yay/lib32-sratom/src/sratom-0.6.4/build'

[==========] Running sratom tests
[ FAILED ] ./sratom_test
[----------] 0/1 tests from sratom.Integration (225 ms total)
[==========] 1 tests from sratom ran (310 ms total)
Failed to run lcov to generate coverage report
[ PASSED ] 0 tests
[ FAILED ] 1 tests

Waf: Leaving directory `/home/tyler/.cache/yay/lib32-sratom/src/sratom-0.6.4/build'
==> ERROR: A failure occurred in check().
Aborting...
Error making: lib32-sratom

tjackson commented on 2019-11-29 04:09

Hi, it seems lv2 is at least a makedepend. The build fails due to missing forge.h, which is provided by lv2.