Info: creating stash file /var/tmp/portage/media-gfx/openscad-2015.03_p2-r3/work/openscad-2015.03-2/.qmake.stash Project MESSAGE: If you're building a development binary, consider adding CONFIG+=experimental Project ERROR: Unknown module(s) in QT: concurrent [ !! ] * Running qmake has failed! (see above for details) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop-plasma_libressl_20171027-191648 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.5.1 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv media-gfx/openscad [ebuild N ] media-gfx/openscad-2015.03_p2-r3 USE="-emacs"
Created attachment 500658 [details] emerge-info.txt
Created attachment 500660 [details] emerge-history.txt
Created attachment 500662 [details] environment
Created attachment 500664 [details] etc.portage.tbz2
Created attachment 500666 [details] media-gfx:openscad-2015.03_p2-r3:20171029-071732.log
Created attachment 500668 [details] temp.tbz2
Looks like dev-qt/qtconcurrent is missing in ebuild dependency tree. So just: emerge -1 dev-qt/qtconcurrent And the configure phase ends up with success. The problem is that the compile process still fails with: i686-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus).
Created attachment 503700 [details] temp dir with logs
I got the same error message ("Project ERROR: Unknown module(s) in QT: concurrent") on my ãmd64 machine; manually merging dev-qt/qtconcurrent solved the problem. I did not experience any further issues ("internal compiler failures"), so from my point of view, it looks like a simple missing dependency...?
For me, when compiler attempts to build objects/cgalutils.o, it enters some 'neverending' process of putting code together, runs entire 1Gig of swap space, entire memory, then finally stops with 'internal compiler failure' message, shown in the build log. Would be great if someone put some light on cgalutils and explain what it depends on.
Update. After adding some extra swap space to the system (8G file), build process goes right till the end and the package installs properly. So huge memory or SWAP space is critical here. I managed to build it with bearly 512 MB of physical RAM...
Author: Michael Weber <xmw@gentoo.org> Date: Sat Dec 9 03:25:38 2017 +0100 media-gfx/openscad: DEPEND on dev-qt/qtconcurrent (thanks Pawel Tatera and Volker Wegert, bug 635758). Package-Manager: Portage-2.3.16, Repoman-2.3.6