Summary: | x11-base/xorg-server: emerge fails on alpha with sys-kernel/linux-headers-2.6.19.2-r1 (and probably some older versions as well) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefaan De Roeck (RETIRED) <stefaan> |
Component: | New packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alpha |
Priority: | High | Keywords: | Inclusion |
Version: | 2006.1 | ||
Hardware: | Alpha | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 159304 | ||
Attachments: | patch that should fix the system-header problems |
Description
Stefaan De Roeck (RETIRED)
2007-01-28 14:46:04 UTC
Created attachment 108370 [details, diff]
patch that should fix the system-header problems
I hope someone can test this with an older sys-kernel/linux-headers version.
This is probably something that should be filed at https://bugs.freedesktop.org as well. Does this remain an issue with 1.3? with older linux-headers version? 1.2 and 1.1 compiled fine with linux-headers-2.6.11-r2 (In reply to comment #3) > Does this remain an issue with 1.3? > Yup. Problem is the new sanitized kernel headers (>=2.6.19 in the tree) which don't include <asm/pci.h> anymore. The patch seems sane to me. @Stefaan: did you check if the patch work against non-sanitized headers (current alpha stable)? If so, please submit the bug to freedesktop. If don't, I can give it a try. Thanks! > @Stefaan: did you check if the patch work against non-sanitized headers > (current alpha stable)? If so, please submit the bug to freedesktop. If don't, > I can give it a try. I've just tried it on my stable box. Portage 2.1.2.9 (default-linux/alpha/2006.1/server, gcc-4.1.2, glibc-2.3.6-r5, 2.6.19-gentoo-r5 alpha), virtual/os-headers: 2.6.11-r4 and it builds fine. Created bug https://bugs.freedesktop.org/show_bug.cgi?id=11648 The patch (or at least an alternate version of it) has been committed upstream. I however have no clue of when it will appear in a release. As the patch is quite straightforward, small, and harmless... I want to pop up the question: could we apply this patch in the ebuild until it appears in a release? Yes, will get to it soon. Just committed to 1.3.0.0, thanks for your patience! |