I am running development-sources 2.6.7. I tried to merge Directfb with +fusion and got the message that linux/fusion.h did not exist and I needed the fusion kernel driver to make this work. Well there isn't one in portage and this ebuild doesn't show one as a dependency. Looking at bugzilla there are references to similar problems and it's fixed somewhere - at least the bugs are marked fixed. How do I get this header file and get multiapp DirectFB working? I upgraded from 2.4 kernel and emerge -s shows that linux-headers-2.4.21-r1 is what is installed. Do I need to upgrade the headers and if so A) why doesn't portage tell me when I do emerge -uD system or world and B) what will break if I do so?
I am now running gentoo-dev-sources. Same problem. With the +fusion flag DirectFB will not compile.
Okay. i fixed it. First get the fusion modules from CVS. Then put fusion.h in /usr/include/linux. Now it will build. I submit the ebuild for DirectRB is broken. Maybe we need DirectRB to depend on an ebuild that installs fusion if +fusion is in the use flags. Fusion has two ways to install - as a module and as a kernel patch so it's added to the menu. Recommended is as a module. Devices also need to be created.
linux-headers install with fusion disabled
I'm not sure I understand what "linux-headers install with fusion disabled" means. Does it mean that the headers install with fusion disabled and I have to activate it somehow? If so how and what do I do?
Hi, I just tried patching the kernel and I think the DirectFB people need to fix the patch. It seems to be out of date. SpanKY: is this why the patch isn't in the kernel? Also, if DirectFB does not work, then it needs to be masked!!! out of x86 and moved to ~x86 end rant
it means the linux-headers packages, by default, do not include fusion support as for masking DirectFB, that's stupid ... just dont enable the non-standard fusion support :p
Yep, your correct... I didn't notice I had this enabled. Removing it seems to have solved the problem... I also had to re-build my kernel once I was finished for everything to work correctly.
i *could* add a check to handle fusion headers not being installed, but that basically solves nothing none of our linux-headers packages install fusion.h (afaik, please correct me if i'm wrong), thus the check will always fail
For me, stable DirectFB-0.9.21 won't build because fusion.h isn't present (error below). ~x86 0.9.22 builds fine, so there seems little point opening a brand new bug - posting here for info. Making all in savage make[3]: Entering directory `/var/tmp/portage/DirectFB-0.9.21/work/DirectFB-0.9.21/gfxdrivers/savage' make[3]: *** No rule to make target `../../src/core/fusion/fusion.h', needed by `savage.lo'. Stop. make[3]: Leaving directory `/var/tmp/portage/DirectFB-0.9.21/work/DirectFB-0.9.21/gfxdrivers/savage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/DirectFB-0.9.21/work/DirectFB-0.9.21/gfxdrivers' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/DirectFB-0.9.21/work/DirectFB-0.9.21' make: *** [all-recursive-am] Error 2
Can DirectFB-0.9.22 go stable? According to comment #9, it fixes the issue described in this bug. For this to happen, looks like you'd need to take care of bug 84348 too. Can't see any other open relevant bugs on DirectFB
fine, 0.9.22 stabilized :P
(In reply to comment #11) > fine, 0.9.22 stabilized :P On my system, 0.9.22 also croaks trying to find "fusion.h". If it matters, I'll post the details, but meanwhile I'm going to turn off the fusion USE flag and get on with my life. :)
