rm -f libQt5SerialPort.so.5.12.2 libQt5SerialPort.so libQt5SerialPort.so.5 libQt5SerialPort.so.5.12 x86_64-pc-linux-gnu-g++ -Wl,-O1 -Wl,--as-needed -Wl,--no-undefined -Wl,--version-script,QtSerialPort.version -Wl,--enable-new-dtags -shared -Wl,-Bsymbolic-functions -Wl,-soname,libQt5SerialPort.so.5 -o libQt5SerialPort.so.5.12.2 .obj/qserialport.o .obj/qserialportinfo.o .obj/qserialport_unix.o .obj/qserialportinfo_unix.o -lQt5Core -lpthread /usr/lib64/libudev.so x86_64-pc-linux-gnu-g++: error: /usr/lib64/libudev.so: No such file or directory make[2]: *** [Makefile:94: ../../lib/libQt5SerialPort.so.5.12.2] Error 1 make[2]: Leaving directory '/var/tmp/portage/dev-qt/qtserialport-5.12.2/work/qtserialport-everywhere-src-5.12.2/src/serialport' make[1]: *** [Makefile:47: sub-serialport-make_first] Error 2 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop_abi32+64_20190403-102005 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * [2] ruby25 (with Rubygems) [3] ruby26 (with Rubygems) Available Rust versions: [1] rust-1.33.0 * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.10.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO dev-qt/qtserialport [ebuild N ] dev-qt/qtserialport-5.12.2 USE="-debug -test"
Created attachment 572254 [details] emerge-info.txt
Created attachment 572256 [details] dev-qt:qtserialport-5.12.2:20190407-223244.log
Created attachment 572258 [details] emerge-history.txt
Created attachment 572260 [details] environment
Created attachment 572262 [details] etc.portage.tbz2
Created attachment 572264 [details] logs.tbz2
Created attachment 572266 [details] temp.tbz2
*** This bug has been marked as a duplicate of bug 673532 ***