Summary: | x11-drivers/xf86-video-intel-2.99.917[udev] error: implicit declaration of function 'fstat' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus <buliwyf1> |
Component: | [OLD] Library | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | alexander, cornicx, eXt, jrmalaq, klaus818, ludo57310, maggu2810, oleid |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Markus
2015-05-30 01:19:08 UTC
Created attachment 404312 [details]
build.log
*** Bug 550766 has been marked as a duplicate of this bug. *** Looks like bug is fixed upstream in commits: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=12af8a575d1518d40416f83195049157c3a062a5 http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=369ceec0e4910ba2c37736a59c55c0d6c26433bf There has been no release since December 2014 unfortunately. *** Bug 551402 has been marked as a duplicate of this bug. *** *** Bug 551462 has been marked as a duplicate of this bug. *** And what can I do? I need this driver for a new installation. You can either use an older gcc or use the patch I provided in bug #550766 as user patch. Could we add the path to the current ebuilds in the portage tree, until a new version is relelased? + 13 Jun 2015; Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> + +files/xf86-video-intel-2.99.917-sna-udev-fstat.patch, + +files/xf86-video-intel-2.99.917-uxa-udev-fstat.patch, + +xf86-video-intel-2.99.917-r1.ebuild: + Add patches to fix building against newer gcc, bug #550784. It works, but now it crashes with sna enabled. It works with uxa enabled. I think the proble "crashs with sna, not with uxa" should be handled in another issue. This one concentrate on the build failures. Am I right? (In reply to Markus Rathgeb from comment #11) > I think the proble "crashs with sna, not with uxa" should be handled in > another issue. This one concentrate on the build failures. > Am I right? Maybe, except for that issue appears when those patches were applied. Also, it broke the previous version of the ebuild. That's weird? Fixing missing includes with the correct system header should not break other stuff. But sure, in general custom patches could break stuff. @ jorgicio : The issue appeared when the patch was introduced? Maybe the new revision just made you compile the driver with a later version of GCC or something like that. As Markus said, this patch can't possible be *directly* responsible for your crashes. If you see crashes, please open a separate bug report. If possible, try to get a backtrace from the X server. (In reply to Chí-Thanh Christopher Nguyễn from comment #15) > If you see crashes, please open a separate bug report. If possible, try to > get a backtrace from the X server. Done. https://bugs.gentoo.org/show_bug.cgi?id=552124 (In reply to Markus from comment #0) > I assume a problem with gcc. since it is the first time I compiled the > package with gcc 4.9.2 (stricter rules ?) I had exactly the same issue with gcc-4.8.4. So this is likely caused by glibc-2.20, not gcc. Please ignore my previous comment. Last successful build om my system was Jun 19. At this point I already had gcc-4.8.4 and glibc-2.20. This bug is triggered by udev-220/systemd-220 and above. Sorry for the noise. :) |