Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 593000

Summary: dev-qt/qt{gui,opengl,printsupport,widgets}-5.7.0[gles2] - opengles2.cpp:49:32: error: glClear was not declared in this scope
Product: Gentoo Linux Reporter: George Diamantopoulos <georgediam>
Component: Current packagesAssignee: Qt Bug Alias <qt>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: qtgui build log
emerge --info output

Description George Diamantopoulos 2016-09-06 16:26:33 UTC
Created attachment 445090 [details]
qtgui build log

I noticed the following errors when rebuilding world with gcc 6.2.0 (from the hardened overlay). The packages that exhibit this are: qtgui-5.7.0, qtopengl-5.7.0, qtprintsupport-5.7.0, qtwidgets-5.7.0.

All aforementioned packages fail during the compile phase with:

avx512.cpp:51:4: error: #error "Feature not supported"
 #  error "Feature not supported"
    ^~~~~
avx512.cpp: In function ‘int main(int, char**)’:
avx512.cpp:61:42: warning: AVX512F vector return without AVX512F enabled changes the ABI [-Wpsabi]
     i = _mm512_maskz_loadu_epi32(0, argv);
                                          ^
gmake: *** [Makefile:163: avx512.o] Error 1
avx512f disabled.

My CFLAGS is set to "-march=skylake -O2 -pipe". According to GCC manual, march=skylake doesn't enable AVX512.

I'm attaching qtgui build log and emerge --info.
Comment 1 George Diamantopoulos 2016-09-06 16:27:29 UTC
Created attachment 445092 [details]
emerge --info output
Comment 2 Michael Palimaka (kensington) gentoo-dev 2016-09-08 19:00:10 UTC
The errors earlier in the log are a normal part of Qt's configuration process.

The final error is more concerning as the gles2 check failed but you have that USE flag enabled.
Comment 3 George Diamantopoulos 2016-09-11 05:07:00 UTC
It seems it must have been a mesa issue (I'm using live mesa). The problem does no longer manifest with current mesa builds. Please close this as invalid.
Comment 4 George Diamantopoulos 2016-09-11 05:08:48 UTC
Nope, my bad. I thought qtnetwork was affected too but I've just tried qtprintsupport and I still get the same...
Comment 5 George Diamantopoulos 2016-10-01 05:34:07 UTC
Now it's gone. So I supposed it could have been a mesa issue.

I'm sorry for the noise generated, please close.