Re: Linker issues for libssw on armel, mips64el and mipsel
On Wed, Aug 12, 2020 at 09:33:31AM +0200, Andreas Tille wrote:
>Hi,
>
>while the package libssw builds nicely on most architectures on armel,
>mips64el and mipsel there is a linking issue[1]:
>
>...
>c -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -I"/include" -I"/include/linux" -I/usr/lib/jvm/default-java/include/ -I/usr/lib/jvm/default-java/include/linux -fPIC -shared -rdynamic -o libsswjni.so sswjni.c ssw.c -Wl,-z,relro -Wl,-z,now
>cc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -o ssw-align main.c kseq.h -L. -lssw -lm -lz -Wl,-z,relro -Wl,-z,now
>/usr/bin/ld: cannot find -lssw
>...
>
>(same on some non-released architectures).
>
>Any idea how to fix this?
Comparing the buildd logs for arm64 and armel, there are obvious
differences - on armel the build doesn't even attempt to make the
library libssw.a. Check the Makefiles etc. to see if it has hard-coded
architecture support?
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"The problem with defending the purity of the English language is that
English is about as pure as a cribhouse whore. We don't just borrow words; on
occasion, English has pursued other languages down alleyways to beat them
unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll
Reply to: