Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 32725

Summary: typo in /usr/include/byteorder.h (kernel gaming-r6) /usr/linux/include/asm-i386/
Product: Gentoo Linux Reporter: Aaron Peterson <alpeterson>
Component: [OLD] Core systemAssignee: x86-kernel (DEPRECATED) <x86-kernel>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Aaron Peterson 2003-11-04 10:27:41 UTC
My kde 3.2beta1 kdemultimedia didn't compile... it complained that there was a
typo in line 38 of my /usr/include/byteorder.h file  before the __

static inline __u64 ___arch__swab64(__u64 val)
is the line

In the gentoo kernel it's static __inline__

so I fixed it in my copy and it works now.
(I'm using r5 but checked out the r6 and the gentoo r8 files... and the problem
is only in gaming sorces)



Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 Tim Yamin (RETIRED) gentoo-dev 2003-11-06 09:46:21 UTC
Erm, is this gaming-sources or the linux-headers?
Comment 2 Harald Kubota 2003-11-23 17:17:49 UTC
linux-headers 2.4.21-r1 has this bug too. Prevented me from emerging kdeultimedia-3.1.4-r1.
I am using vanilla-sources, so it's clearly not related to gaming-sources.
Comment 3 Harald Kubota 2003-11-23 23:07:20 UTC
Hmm...nur sure what the bug is here. There are awfully lot of "__inline__" as well as "inline" in /usr/include/asm. My knowledge of gcc inline assember is virtually noneexistant.
The old headers (2.4.19-r1) had no ___arch__swab64 defined, thus the problem was none and is still none for thuse using not ARCH="~x86".
I finally was able to emerge kdemultimedia-3.1.4-r1 by using byteorder.h from the 2.4.19-r1 includes.
Comment 4 Tim Yamin (RETIRED) gentoo-dev 2003-11-24 09:35:08 UTC
Looks like these header changes of theirs are causing ANSI non-conformance... I'm duplicating this as bug #32246 as that is where the issue lies, but feel free to reopen this if something else arrives.

*** This bug has been marked as a duplicate of 32246 ***