Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

Hi, Is it correct that we also need an additional build-depends on libatomic-ops-dev ? Christoph Am 06.04.2017 um 15:30 schrieb Radovan Birdic: > Hi, > > I have created and attached a patch that enables linking with latomic library > as needed. > > When ntirpc package is recompiled with this

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

Control: tags -1 patch > I will report separate bug for nfs-ganesha, linking with latomic > library should solve this issue as well. Whoops, I overlooked your mail. Yes, this looks like the proper fix and I suggest using this solution for the aforementioned reasons. Thanks for the quick action!

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

> This is a bug that will hit everyone who wants to use libntirpc > on mips or mipsel: And powerpc and powerpcspe :). And possibly more. I would suggest linking with --as-needed which resolves in a more generic way as compared to adding "-latomic" to a whitelist of architectures. Please see the

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

Hi, I have created and attached a patch that enables linking with latomic library as needed. When ntirpc package is recompiled with this patch, the above-mentioned problem is solved, but after that, new problem occurs on ganesha.nfsd linking: > /usr/bin/ld: libMainServices.a(client_mgr.c.o):

Bug#859689: libntirpc must be linked with libatomic on mips and mipsel

Package: libntirpc1.4 Version: 1.4.1-1 Severity: serious Control: affects -1 src:nfs-ganesha nfs-ganesha FTBFS on mips and mipsel: https://buildd.debian.org/status/package.php?p=nfs-ganesha=sid ... [ 55%] Linking C executable sm_notify.ganesha cd