[SOLVED] Internal Compiler Error trying to compile qt5 and PyQt5

maew · 11-08-2016, 07:52 AM

Hello all,

The issue was overheating.

I am experimenting with freeslack on Librem 15,
It's a fresh install, slackpkg upraded-it-all (using freeslack's mirror). Trying to get qutebrowser I went on compiling most of the dependencies from SBo repositories.
I first had a segmentation fault compiling qt5. and went around it using AlienBob's build. Same story with qt5-webkit.
Now I am trying to compile PyQt5 and I got the following:

Code:

In file included from /usr/include/c++/5.3.0/bits/basic_ios.h:37:0,
                 from /usr/include/c++/5.3.0/ios:44,
                 from /usr/include/c++/5.3.0/ostream:38,
                 from /usr/include/c++/5.3.0/iterator:64,
                 from /usr/include/qt5/QtCore/qbytearray.h:53,
                 from /usr/include/qt5/QtCore/qmetatype.h:46,
                 from /usr/include/qt5/QtCore/QMetaType:1,
                 from sipAPIQtLocation.h:30,
                 from sipQtLocationQPlaceIdReply.cpp:24:
/usr/include/c++/5.3.0/bits/locale_facets.h:1587:75: internal compiler error: Illegal instruction
     _S_format_float(const ios_base& __io, char* __fptr, char __mod) throw();
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Makefile:820: recipe for target 'sipQtLocationQPlaceIdReply.o' failed
make[1]: *** [sipQtLocationQPlaceIdReply.o] Error 1
make[1]: Leaving directory '/tmp/SBo/PyQt5_gpl-5.6/QtLocation'
Makefile:1457: recipe for target 'sub-QtLocation-make_first-ordered' failed
make: *** [sub-QtLocation-make_first-ordered] Error 2

Also I compiled python3-sip from slackbuilds.

I am not sure where the issue could come from.
QMake version 3.0
Using Qt version 5.7.0 in /usr/lib64

Any ideas?

Thank you for your time

phenixia2003 · 11-08-2016, 08:17 AM

Hello,

According to this thread, this might be an hardware issue.

--
SeB

Emerson · 11-08-2016, 08:26 AM

What CPU are you using, is it in a virtual machine?

maew · 11-08-2016, 08:34 AM

Quote:

Originally Posted by phenixia2003

According to this thread, this might be an hardware issue.

So it could be that the hardware is defectuous...

Quote:

Originally Posted by Emerson

What CPU are you using, is it in a virtual machine?

Code:

bash-4.3# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 61
Model name:            Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
...
Flags:                 fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap xsaveopt

It's not on a virtual machine, it is on a laptop.

Emerson · 11-08-2016, 08:48 AM

It is a long shot, but do you load CPU microcode at the boot?

maew · 11-08-2016, 08:51 AM

Quote:

Originally Posted by Emerson

It is a long shot, but do you load CPU microcode at the boot?

I have no idea how to check that.. :s

Emerson · 11-08-2016, 09:00 AM

Never mind then, if you retry the build, do you get the exact same error in exactly same place?

maew · 11-08-2016, 09:21 AM

Quote:

Originally Posted by Emerson

Never mind then, if you retry the build, do you get the exact same error in exactly same place?

It's compiling, will tell you when it gets there

maew · 11-08-2016, 09:25 AM

No. That went faster than expected..

Code:

In file included from /usr/include/c++/5.3.0/random:42:0,
                 from /usr/include/c++/5.3.0/bits/stl_algo.h:66,
                 from /usr/include/c++/5.3.0/algorithm:62,
                 from /usr/include/qt5/QtCore/qglobal.h:94,
                 from /usr/include/qt5/QtCore/qmetatype.h:44,
                 from /usr/include/qt5/QtCore/QMetaType:1,
                 from sipAPIQtCore.h:30,
                 from sipQtCoreQResource.cpp:24:
/usr/include/c++/5.3.0/limits:1734:10: internal compiler error: Segmentation fault
        = round_to_nearest;
          ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Makefile:2128: recipe for target 'sipQtCoreQResource.o' failed
make[1]: *** [sipQtCoreQResource.o] Error 1
make[1]: Leaving directory '/tmp/SBo/PyQt5_gpl-5.6/QtCore'

Somewhere in the compil output it says : The Python dbus module doesn't seem to be installed.
could that be a reason to fail the compil?

EDIT2:
tried again:
/usr/include/c++/5.3.0/limits:1659:10: internal compiler error: Segmentation fault
= round_to_nearest;
^

Emerson · 11-08-2016, 09:51 AM

Hardware overheating.

phenixia2003 · 11-08-2016, 09:54 AM

Hello,

Quote:

Originally Posted by maew

No. That went faster than expected..

Code:

In file included from /usr/include/c++/5.3.0/random:42:0,
                 from /usr/include/c++/5.3.0/bits/stl_algo.h:66,
                 from /usr/include/c++/5.3.0/algorithm:62,
                 from /usr/include/qt5/QtCore/qglobal.h:94,
                 from /usr/include/qt5/QtCore/qmetatype.h:44,
                 from /usr/include/qt5/QtCore/QMetaType:1,
                 from sipAPIQtCore.h:30,
                 from sipQtCoreQResource.cpp:24:
/usr/include/c++/5.3.0/limits:1734:10: internal compiler error: Segmentation fault
        = round_to_nearest;
          ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Makefile:2128: recipe for target 'sipQtCoreQResource.o' failed
make[1]: *** [sipQtCoreQResource.o] Error 1
make[1]: Leaving directory '/tmp/SBo/PyQt5_gpl-5.6/QtCore'

I suggest you to check your cpu temperature. In the bios for instance or by running the command below :

Code:

$ sensors

If you get this message :

Code:

Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

as root, run the command modprobe coretemp, then re-run the command sensors

if you get the same message as earlier, then, run, as root, the command sensors-detect and validate default answer to each question. At the end, it will give you a list of command as below :

Code:

#----cut here----
# Chip drivers
modprobe coretemp
modprobe <module-specific-to-your-computer>
/usr/bin/sensors -s
#----cut here----

At this point, run, as root, each of the commands that sensors-detect has returned, and run the command sensors, which should give you something like that :

Code:

$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +35.0°C  (high = +85.0°C, crit = +105.0°C)
Core 0:         +30.0°C  (high = +85.0°C, crit = +105.0°C)
Core 1:         +33.0°C  (high = +85.0°C, crit = +105.0°C)
Core 2:         +30.0°C  (high = +85.0°C, crit = +105.0°C)
Core 3:         +34.0°C  (high = +85.0°C, crit = +105.0°C)

P.S: The best would be to run sensors before and after compilation.

--
SeB

maew · 11-08-2016, 10:03 AM

I'll let the computer cool a bit and run the sensors test before and after.. from what I have seen, during compilation the temperature oscilates between 72C and 80C

Emerson · 11-08-2016, 11:00 AM

CPU is just one part that can overheat. 80° C is rather hot, I do not let my laptop go over 70° C. I switch over to powersave governor to keep the temperature down when needed.

maew · 11-09-2016, 04:48 AM

I didn't know till now but it already is in governor powersave

Code:

root@slackship:/# cat /sys/devices/system/cpu/cpufreq/policy?/scaling_governor 
powersave
powersave
powersave
powersave

Actually I just tried to compile again and even with the CPU's at 55C I just got
/usr/include/c++/5.3.0/limits:1809:13: internal compiler error: Segmentation fault
round_to_nearest;

EDIT: trying again with an icepack under the laptop...

Emerson · 11-09-2016, 05:04 AM

It is a little confusing, newer Intel processors are handled differently. Powersave actually acts as ondemand. Check it out with cpupower utility.