As described by bug #2871280 and #2797884 at the freeglut bug tracking site [1], there are quite basic bugs in freeglut-2.6.0 that were not present in 2.4.0. Hence it is unclear to me why this version has been marked as stable wrt to bug #282290 (stabilization of xorg-server-1.6.3) as noted in portage ChangeLog file. As an illustration take the simple code attached and look at the segfault produced by a simple glutCreateWindow. Note that this code worked with freeglut-2.4. In my opinion it should be re-considered to keyword freeglut-2.6 again. [1] https://sourceforge.net/tracker/?func=browse&group_id=1032&atid=101032 Reproducible: Always Steps to Reproduce: g++ main.cpp -lglut -o main; ./main
Created attachment 205762 [details] simple crashing code
Sorry, but for some strange reason glutInit* were renamed to glutit*. Please take this into account.
Reverted back to ~amd64. Thanks for reporting.
This doesn't crash for me and I've compiled and tested a number of other OpenGL examples and tutorials with freeglut-2.6.0, so could you (Stefan) please test again? Maybe there was just something weird with your set-up at the time. If some others could test too that would be great. FYI I'm using gcc-4.3.4 and glibc-2.10.1. freeglut-2.4.0 is from 2005, it would be really nice to stabilize 2.6.0.
I confirm that the problem is gone now and I also left a note at the freeglut bug tracker (which never got attention). Due to the old call stack I guess that there was an interference with the Intel drivers. Since Oct 2009 a few Intel driver versions passed by and one of them may have resolved the problem. On my amd64 system I currently use: xf86-video-intel-2.9.1, mesa-7.7.1, glibc-2.10.1-r1, gcc-4.4.3-r2
