Created attachment 362534 [details] build.log Not really sure what is going on here, but econf dies and spits out an error message which isn't useful to me. Fails for both my amd64 and x86 builds. kernel configs here: https://code.google.com/p/pentoo/source/browse/livecd/trunk/amd64/kernel/config-3.9.9 https://code.google.com/p/pentoo/source/browse/livecd/trunk/x86/kernel/config-3.9.9
This looks oddly alike to bug 484142. Though: - log looks filtered (IIRC, econf should be echoed) - perhaps not in this case, but usually config.log would have been of use
Can you attach config.log?
Created attachment 362576 [details] config.log sorry, I would have had this earlier but this is one of those files that magically disappears when catalyst explodes and unmounts my tmpfs.
/usr/include/xorg/dri.h:41:21: fatal error: xf86dri.h: No such file or directory Hm, not sure why that is. Is x11-proto/xf86driproto installed?
(In reply to Chí-Thanh Christopher Nguyễn from comment #4) > /usr/include/xorg/dri.h:41:21: fatal error: xf86dri.h: No such file or > directory > > Hm, not sure why that is. Is x11-proto/xf86driproto installed? By the time catalyst dies it definitely is installed: obj /usr/include/X11/dri/xf86dri.h 86e207e17bb0f060774c8ddd3a6fb467 1374050746 xf86driproto-2.1.1 is in /var/db/pkg I am running with portage --jobs=32 so it is heavily parallel but it doesn't *appear* to me that this was installed after the failure, it looks like the failure was the last thing to occur because the build died.
Created attachment 362582 [details, diff] patch I think this upstream patch is what you want. http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=6004870d53221caf05a330fcfc8a72e68b2b8898
(In reply to Matt Turner from comment #6) But that patch is supposedly already in 2.21.15
(In reply to Chí-Thanh Christopher Nguyễn from comment #7) > (In reply to Matt Turner from comment #6) > But that patch is supposedly already in 2.21.15 And in fact I confirmed that patch is in 2.21.15 two days ago ;-)
Does my suggestion from bug 484142 help ?
(In reply to Rafał Mużyło from comment #9) > Does my suggestion from bug 484142 help ? I don't see any suggestions which really apply to my situation as it looks like you expected it to just work. What I do notice is that my xorg version is only 1 rev away from the original reporter of that bug: x11-base/xorg-server-1.12.4-r2 Perhaps there is an issue there?
@Rick, sorry for not getting back to you sooner. Could you try running 'pkg-config --debug xf86driproto' inside your catalyst chroot after the build failure? And could you try to build an image without the --jobs portage options? I have no idea if this is going to help, but let's just rule it out. Thanks
(In reply to Rémi Cardona from comment #11) > @Rick, sorry for not getting back to you sooner. > > Could you try running 'pkg-config --debug xf86driproto' inside your catalyst > chroot after the build failure? And could you try to build an image without > the --jobs portage options? I have no idea if this is going to help, but > let's just rule it out. > > Thanks tested without --jobs, as expected, no change. Nu / # pkg-config --debug xf86driproto pkgconf: unknown option -- debug
pkgconf does not support --debug, only pkg-config does.
I've fixed 2.21.15 in portage and I'm sending a patch upstream to get it fixed in git. Hopefully, it could be fixed for 3.0. Thanks
