Bug 50036

Summary:	linux-headers/linux-headers-2.6.5.ebuild -needs- to be unmasked for amd64
Product:	Gentoo Linux	Reporter:	Ryan Earl <heretic>
Component:	New packages	Assignee:	AMD64 Project <amd64>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Ryan Earl 2004-05-04 15:39:53 UTC

This following documents says to ask for "~amd64" to be added to the header of linux-headers/linux-headers-2.6.5.ebuild, but shouldn't it be "amd64"? 
http://www.gentoo.org/proj/en/base/amd64/technotes.xml?part=1&chap=4#doc_chap1

I would rate this bug above enchancement because the 2.4 kernel has been deprecated in AMD64 according to some documentation.  Therefore it shouldn't default to the 2.4 kernel headers.  gentoo-dev-sources are currently on 2.6.5-r1.  Using 2.4 headers could mess up glibc compilation.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Travis Tilley (RETIRED) gentoo-dev

2004-05-05 00:19:14 UTC

2.4 headers wont mess anything up. however, many apps break when using 2.6 headers. 2.6 headers simply will not be unmasked for any arch at this time.

feel free to submit fixes for sash or any of the other apps that are totally destroyed by 2.6  kernel headers. even so, i doubt you can test and fix every app in portage that breaks... so why upgrade to the 2.6 headers at all if everything works fine already? the 2.4 /kernel/ is deprecated, and for totally unrelated reasons (like devfs being broken, something that has zero effect on using 2.4 headers in userspace applications).