Source: redland-bindings Version: 1.0.17.1+dfsg-1.3 Severity: serious Tags: bullseye sid ftbfs
I was looking at #966787, and while the fix for that bug should be easy (just remove python-librdf's hardcoded python dependency), I could not build the package in a current amd64 sid chroot: ,---- | gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/rasqal -I/usr/include/raptor2 -DSWIG_PYTHON_SILENT_MEMLEAK -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security Redland_wrap.so -Wl,-z,relro -lrdf -lrasqal -lraptor2 -o _Redland | /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/Scrt1.o: in function `_start': | (.text+0x20): undefined reference to `main' | /usr/bin/ld: Redland_wrap.so: in function `SWIG_Python_ErrorType': | ./python2.7/./Redland_wrap.c:955: undefined reference to `PyExc_IOError' | /usr/bin/ld: ./python2.7/./Redland_wrap.c:952: undefined reference to `PyExc_MemoryError' `---- In the last successful build[1], the corresponding gcc commandline used "-shared" and ended with "-o _Redland.so" rather "-o _Redland", so trying to build an executable is apparently want went wrong here. A build log is attached for reference. 1. https://buildd.debian.org/status/fetch.php?pkg=redland-bindings&arch=amd64&ver=1.0.17.1%2Bdfsg-1.3%2Bb9&stamp=1584636898&raw=0
redland-bindings_1.0.17.1+dfsg-1.3_amd64.build.xz
Description: application/xz
