Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#63334 - [libidn] tests are failing
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Wednesday, 31 July 2019, 19:12 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 31 January 2022, 17:06 GMT
Opened by Andreas Baumann (andreas_baumann) - Wednesday, 31 July 2019, 19:12 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 31 January 2022, 17:06 GMT
|
DetailsDescription:
../build-aux/test-driver: line 107: 18964 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-thread_create Additional info: * package version(s): 1.35-1 Steps to reproduce: asp export libidn cd libidn staging-x86_64-build |
This task depends upon
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925746
Something about a test function symbol which runs away due to removing unused symbols.
/etc/makepkg.conf contains:
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
So I have to find a way to counteract that for the test programs.
My workaroud for now is setting in PKGBUILD:
build() {
cd ${pkgname}-${pkgver}
export LDFLAGS="-Wl,-O1,--sort-common,-z,relro,-z,now"
./configure --prefix=/usr
make
}
check() {
cd ${pkgname}-${pkgver}
export LDFLAGS="-Wl,-O1,--sort-common,-z,relro,-z,now"
make check
}
This is just a workaround, the root cause is the tests in libidn
playing funny tricks with the linker..
Same goes for libunistring.