Created attachment 712665 [details] build.log QTGUI complains of a missing processor feature RTM.
Created attachment 712668 [details] CPUID
Created attachment 712671 [details] Portage config
same mistake processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz stepping : 1 microcode : 0x26 cpu MHz : 800.289 cache size : 4096 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid : 3 initial apicid : 3 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes 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 cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx 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 cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d vmx flags : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple shadow_vmcs bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit srbds bogomips : 4602.94 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:
FWIW, everyone who I've spoken to who has managed to hit this was able to resolve it by re-emerging dev-qt/qtcore then all of dev-qt/*.
(In reply to Sam James from comment #4) > FWIW, everyone who I've spoken to who has managed to hit this was able to > resolve it by re-emerging dev-qt/qtcore then all of dev-qt/*. while I remember: we saw a few more people hitting this after a microcode update disabled some functionality in Intel processors (e.g. https://forums.gentoo.org/viewtopic-t-1146141-highlight-rtm.html), but think we had more in #gentoo too. I don't have a great idea for how to handle this other than possibly slipping in whatever the relevant disable feature config option is when we next do a version bump, to ensure everything is built consistently w/o it. This functionality is kind of considered a failure anyway so I don't think it's like we'd be penalising users for one CPU manufacturer's issues.
*** Bug 939846 has been marked as a duplicate of this bug. ***
