Created attachment 463910 [details] emerge --info After DirectFB package update (dev-libs/DirectFB-1.4.9-r1 -> DirectFB-1.7.6) I got errors while trying to get sys-apps/qingy-1.0.0-r2 to work (it works only in text-mode). With qingy debug log-level I got these errors while entering login-screen: Direct/Modules unable to dlopen libdirectfb_mesa_system.so ... undefined symbol glEGLImageTargetRenderbufferStorageOES The problem is that current dev-libs/DirectFB-1.7.6 has separate "egl" USE-flag (no such dependency in sys-apps/qingy-1.0.0-r2 ebuild). But when I tried to set it in package.use and recompile DirectFB I got the situation as in https://bugs.gentoo.org/show_bug.cgi?id=540644 Temporary solution: mask and downgrade to dev-libs/DirectFB-1.4.9-r1 -- sys-apps/qingy-1.0.0-r2 works well with it. Bugs/questions: 1. No "egl" USE-flag in sys-apps/qingy-1.0.0-r2 ebuild (at least for dev-libs/DirectFB-1.7.6) 2. What to do with future DirectFB updates? (the solution to disable "egl" USE-flag from #540644 is unacceptable here)
Created attachment 510834 [details] Compilation error with GCC 6.4 I can confirm. DirectFB have a problem with EGL.
I currently have DirectFB-1.7.6 installed. I do not have the egl flag set. I did try setting the egl flag and of course it fails to build. However... I masked qingy-1.0.0-r3 and re-emerged 1.0.0-r2 because qingy with graphics is my preference. I did not downgrade DirectFB. I am still using 1.7.6. This is working just fine for me. I have qingy with a graphical theme just as before. If I understand right this ticket says that DirectFB support was removed from the qingy ebuild because it was thought to require DirectFB to be built with egl which currently is not possible. If so then I do not understand how that can be since it is working for me. Are there any files or output I can attach in order to show why it is working on my computer in order to help get graphics support restored to the qingy ebuild?
I am running qingy and I have DirectFB without EGL use flag and it works OK. So I do not understand why you removed the directfb use flag. Just to workaround DirectFB bug that it doesn't compile with EGL? This bug should be fixed in DirectFB. Other packages shoudn't drop DirectFB support just because currently DirectFB doesn't compile with the EGL, which is optional. If reporter has problem with DirectFB, he can compile qingy without directfb use flag, but I do not see the point in removing the DirectFB support for everybody. Moreover the description of "sys-apps/qingy" is "A DirectFB getty replacement", so having it without DirectFB support is quite silly.
FYI I have dev-libs/DirectFB-1.7.6. I tried to recompile both DirectFB and qingy and everything works as it should.
(In reply to Andrew Kanner from comment #0) > > Direct/Modules unable to dlopen libdirectfb_mesa_system.so > ... > undefined symbol glEGLImageTargetRenderbufferStorageOES > For me this seems like bug in Mesa, where some part of EGL support was compiled in even with --disable-egl (i.e. [-egl] use flag). But it seems this bug has been already resolved, so could you please return the directfb use flag to qingy?
This makes a couple of us that are running Qingy with DirectFB just fine. While there may be a bug regarding EGL and DirectFB this does not seem to have anything to do with Qingy. Shouldn't this bug be dealt with in the DirectFB ebuild? Why does it make any sense to cripple Qingy? Could we please get DirectFB support restored in Qingy now?
Now the old, perfectly working Qingy ebuild is removed! Why do you hate Qingy?
Created attachment 529278 [details] Good Qingy Ebuild Here is the old, perfectly good Qingy ebuild for anyone who still wants to use it with DirectFB
I opened bug 658234. Please re-enable the DirectFB support.
DirectFB is gone.
