Re: unknown linker error

[Mark Davies <mark%ecs.vuw.ac.nz@localhost>]

Yesterday I wrote:
> I'm in the process of trying to update the qt5 packages to 5.7.1 and I'm
> making progress but just hit an error I've never seen before:
>
> [...]
> libtool --silent --mode=link c++ -version-info 12:1:7 -rpath
> /usr/pkg/qt5/lib -lexecinfo -lkvm -L/usr/pkg/lib -Wl,-R/usr/pkg/lib
> -L/usr/lib -Wl,-R/usr/lib -Wl,--version-script,QtPrintSupport.version
> -pthread -Wl,-rpath,/usr/pkg/qt5/lib -shared -Wl,-Bsymbolic-functions -o
> ../../lib/libQt5PrintSupport.la .obj/qpaintengine_alpha.lo
> .obj/qpaintengine_preview.lo .obj/qprintdevice.lo
> .obj/qprintengine_pdf.lo .obj/qprinter.lo .obj/qprinterinfo.lo
> .obj/qplatformprintdevice.lo .obj/qplatformprintplugin.lo
> .obj/qplatformprintersupport.lo .obj/qcups.lo
> .obj/qprintpreviewwidget.lo .obj/qcupsjobwidget.lo
> .obj/qprintdialog_unix.lo .obj/qpagesetupdialog_unix.lo
> .obj/qabstractprintdialog.lo .obj/qpagesetupdialog.lo
> .obj/qprintpreviewdialog.lo .obj/qrc_qprintdialog.lo
> .obj/moc_qplatformprintplugin.lo .obj/moc_qcupsjobwidget_p.lo
> .obj/moc_qabstractprintdialog.lo .obj/moc_qpagesetupdialog_unix_p.lo
> -L/usr/pkg/lib
> -L/src/work/pkgsrc/x11/qt5-qtbase/work.x86_64/qtbase-opensource-src-5.7.1/lib
> -lQt5Widgets -L/usr/lib -lQt5Gui -lQt5Core -lexecinfo -lkvm
> -Wl,-R/usr/pkg/lib -lGL
> ld: BFD (NetBSD Binutils nb1) 2.23.2 assertion fail
> /src/work/7/src/external/gpl3/binutils/dist/bfd/elflink.c:2547
> ld: BFD (NetBSD Binutils nb1) 2.23.2 assertion fail
> /src/work/7/src/external/gpl3/binutils/dist/bfd/elflink.c:2547
> Makefile:244: recipe for target
> '../../lib/../../lib/libQt5PrintSupport.la' failed
>
> anyone know what this is complaining about? (this is on 7.0_STABLE)

Further probing has told me that the assertion on line 2547 is

          BFD_ASSERT (weakdef->root.type == bfd_link_hash_defined
                      || weakdef->root.type == bfd_link_hash_defweak);


and that the problem is with libQt5Widgets.so and that if I build a 
libQt5Widgets without qscroller.o in it then the complaint goes away
but I still don't know what the actual issue is or whats changed from 5.5.

cheers
mark