On Sat, Jan 20, 2018 at 12:28:49AM +0100, David Haller wrote: > Hello, > > On Fri, 19 Jan 2018, Christoph Böhmwalder wrote: > >I tried building qtdeclarative-5.9.3 today, but the linker failed: > > > >$ cat build.log > >g++-6.4.0 -Wl,-O1 -Wl,--as-needed -Wl,--enable-new-dtags -shared -o > >libparticlesplugin.so .obj/plugin.o > >-L/var/tmp/portage/dev-qt/qtdeclarative-5.9.3/work/qtdeclarative-opensource-src-5.9.3/lib > > -lQt5QuickParti > >cles -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lGL -lpthread > >/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../lib64/libQt5Gui.so:(*IND*+0x0): > > multiple definition of > > `__bss_start' > [..] > > From the build log it seems you have compiled Qt5Gui (etc.) with > g++-7.2.0, and now try to use g++-6.4.0. I don't think that works. Ah yeah, I forgot to turn that off. I have an env file that switches to gcc-6.4.0 for use with old standalone packages that don't support 7.2.0 yet (I really don't use it anymore nowadays though).
> Try again using 7.2.0 (unless you want to recompile qt with 6.4.0 > again). Anyways, this leads to the exact same error, so I'm inclined to think it has nothing to do with gcc versions. I was however concerned about Qt versions clashing (4 vs 5?). In fact, I just double-checked qtchooser, and this is the output: $ qtchooser -l 4 5 default qt4-i686-pc-linux-gnu qt4-x86_64-pc-linux-gnu qt4 qt5-x86_64-pc-linux-gnu qt5 Does this mean Qt4 is prioritized over Qt5? That would be a problem in this case, right? -- Regards, Christoph
