Public bug reported:
https://launchpadlibrarian.net/441262641/buildlog_ubuntu-
eoan-i386.liblockfile_1.15-1_BUILDING.txt.gz
gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -fPIC -shared
-Wl,-soname,liblockfile.so.1 \
-o liblockfile.so lockfile.o -lc
gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_GNU_SOURCE -fPIC -D_REENTRANT -I.
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o dotlockfile.o dotlockfile.c
gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_GNU_SOURCE -fPIC -D_REENTRANT -I. -c
lockfile.c -o xlockfile.o
lockfile.c: In function ‘lockfile_create_save_tmplock’:
lockfile.c:350:9: warning: ignoring return value of ‘link’, declared with
attribute warn_unused_result [-Wunused-result]
350 | (void)link(tmplock, lockfile);
| ^~~~~~~~~~~~~~~~~~~~~~~
gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -o dotlockfile dotlockfile.o
xlockfile.o
./run-tests.sh
lockfile still exists after unlock
make[1]: *** [Makefile:88: test-stamp] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:7: build-arch] Error 255
** Affects: liblockfile (Ubuntu)
Importance: High
Status: Confirmed
** Tags: ftbfs rls-ee-incoming
** Changed in: liblockfile (Ubuntu)
Status: New => Confirmed
** Changed in: liblockfile (Ubuntu)
Importance: Undecided => High
** Tags added: ftbfs rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to liblockfile in Ubuntu.
https://bugs.launchpad.net/bugs/1843748
Title:
liblockfile ftbfs in eoan (i386 only)
Status in liblockfile package in Ubuntu:
Confirmed
Bug description:
https://launchpadlibrarian.net/441262641/buildlog_ubuntu-
eoan-i386.liblockfile_1.15-1_BUILDING.txt.gz
gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -fPIC -shared
-Wl,-soname,liblockfile.so.1 \
-o liblockfile.so lockfile.o -lc
gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_GNU_SOURCE -fPIC -D_REENTRANT -I.
-Wdate-time -D_FORTIFY_SOURCE=2 -c -o dotlockfile.o dotlockfile.c
gcc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_GNU_SOURCE -fPIC -D_REENTRANT -I. -c
lockfile.c -o xlockfile.o
lockfile.c: In function ‘lockfile_create_save_tmplock’:
lockfile.c:350:9: warning: ignoring return value of ‘link’, declared with
attribute warn_unused_result [-Wunused-result]
350 | (void)link(tmplock, lockfile);
| ^~~~~~~~~~~~~~~~~~~~~~~
gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -o dotlockfile dotlockfile.o
xlockfile.o
./run-tests.sh
lockfile still exists after unlock
make[1]: *** [Makefile:88: test-stamp] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:7: build-arch] Error 255
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liblockfile/+bug/1843748/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
