Created attachment 440228 [details] build.log Am able to workaround for now by doing: LIBS="-ldl" emerge -1 networkmanager
(In reply to Rick Harris from comment #0) > Created attachment 440228 [details] > build.log > > Am able to workaround for now by doing: > LIBS="-ldl" emerge -1 networkmanager For me the cause was under-linking caused by using the gold linker - there was no problem when I switched to ld.bfd for this version of networkmanager.
(In reply to Adrian.Bassett from comment #1) > (In reply to Rick Harris from comment #0) > > Created attachment 440228 [details] > > build.log > > > > Am able to workaround for now by doing: > > LIBS="-ldl" emerge -1 networkmanager > > For me the cause was under-linking caused by using the gold linker - there > was no problem when I switched to ld.bfd for this version of networkmanager. FWIW I'm not using ld.gold, using standard ld.bfd when build fails in this way. Even just extracting upstream's vanilla tarball and issuing a './configure && make' on the source it fails in exactly the same way. It seems maybe an oversight by upstream in libnm/Makefile.in leaving out '$(LIBDL)' in libnm.la: link line. Changing: $(AM_V_CCLD)$(libnm_la_LINK) -rpath $(libdir) $(libnm_la_OBJECTS) $(libnm_la_LIBADD) $(LIBS) to be: $(AM_V_CCLD)$(libnm_la_LINK) -rpath $(libdir) $(libnm_la_OBJECTS) $(libnm_la_LIBADD) $(LIBS) $(LIBDL) prior to running configure, means a successful build.
Created attachment 440318 [details, diff] missing-libdl-link-fix.patch
(In reply to Rick Harris from comment #3) > Created attachment 440318 [details, diff] [details, diff] > missing-libdl-link-fix.patch Interesting - but changing the linker was the only thing I did. (Perhaps mine was a niche case but I am a little bit surprised that there aren't more people having problems if this software is as much installed as I assume it is.)
(In reply to Adrian.Bassett from comment #4) > (In reply to Rick Harris from comment #3) > > Created attachment 440318 [details, diff] [details, diff] [details, diff] > > missing-libdl-link-fix.patch > > Interesting - but changing the linker was the only thing I did. > > (Perhaps mine was a niche case but I am a little bit surprised that there > aren't more people having problems if this software is as much installed as > I assume it is.) Maybe both our cases are special. I'm always finding new and interesting ways to break stuff :) Bit surprised also but this version hasn't been in the tree more than a few days so probably time will tell.
(In reply to Adrian.Bassett from comment #1) > (In reply to Rick Harris from comment #0) > > Created attachment 440228 [details] > > build.log > > > > Am able to workaround for now by doing: > > LIBS="-ldl" emerge -1 networkmanager > > For me the cause was under-linking caused by using the gold linker - there > was no problem when I switched to ld.bfd for this version of networkmanager. Can confirm this. With gold the build fails. Switching to bfd linker works for me.
My bad I was unaware that my system was in fact using ld.gold. Long boring story but I had mistakenly set and forgot EXTRA_ECONF="--enable-gold=default" in /etc/portage/... This meant the readlink command I was using to detect the currently used 'ld' would display inaccurately and I actually needed to do 'ld -v' to find out it was set to 'gold'. *sigh* Sorry for the noise, closing now...
It is still a bug that needs fixing.
Also ran into this. Is there a way to force ld.bfd in the ebuild?
(In reply to Jason Schulz from comment #9) > Also ran into this. Is there a way to force ld.bfd in the ebuild? Yes, but that's a workaround, not a fix.
I see NM-1.2.4 was released, which includes the upstream fix for this. I'll bump it.
commit 0c690a07eb4b9a1b013691255bfd1671212fc9e7 Author: Mike Gilbert <floppym@gentoo.org> Date: Wed Aug 3 21:25:57 2016 -0400 net-misc/networkmanager: bump to 1.2.4 Package-Manager: portage-2.3.0_p16 net-misc/networkmanager/Manifest | 1 + .../networkmanager/networkmanager-1.2.4.ebuild | 322 +++++++++++++++++++++ 2 files changed, 323 insertions(+)
