Bug#183081: libc6-dev: hppa: bug in byteorder.h and swab.h
Package: libc6-dev
Version: 2.3.1-14
Severity: normal
I noticed this problem when the autobuilding of one of my packages failed:
In file included from /usr/include/linux/cdrom.h:14,
from audiocd.h:33,
from cddbaccessdialog.h:31,
from cddbaccessdialogdata.cpp:10:
/usr/include/asm/byteorder.h:43: syntax error before `(' token
/usr/include/asm/byteorder.h:46: `x' was not declared in this scope
/usr/include/asm/byteorder.h:47: `t1' was not declared in this scope
/usr/include/asm/byteorder.h:47: `int ___arch__swab32' redeclared as different
kind of symbol
/usr/include/asm/byteorder.h:9: previous declaration of `const __u32
___arch__swab32(unsigned int)'
/usr/include/asm/byteorder.h:48: redefinition of `int ___arch__swab32'
/usr/include/asm/byteorder.h:47: `int ___arch__swab32' previously defined here
/usr/include/asm/byteorder.h:49: syntax error before `return'
In file included from /usr/include/linux/byteorder/big_endian.h:11,
from /usr/include/asm/byteorder.h:73,
from /usr/include/linux/cdrom.h:14,
from audiocd.h:33,
from cddbaccessdialog.h:31,
from cddbaccessdialogdata.cpp:10:
/usr/include/linux/byteorder/swab.h: In function `const __u32
__fswab32(unsigned int)':
/usr/include/linux/byteorder/swab.h:146: `___arch__swab32' cannot be used as a
function
/usr/include/linux/byteorder/swab.h: In function `__u32 __swab32p(__u32*)':
/usr/include/linux/byteorder/swab.h:150: `___arch__swab32' cannot be used as a
function
/usr/include/linux/byteorder/swab.h: In function `void __swab32s(__u32*)':
/usr/include/linux/byteorder/swab.h:154: `___arch__swab32' cannot be used as a
function
Full build log is at:
http://buildd.debian.org/fetch.php?&pkg=kcdlabel&ver=2.11-KDE3-1&arch=hppa&stamp=1046564305&file=log&as=raw
-- System Information:
Debian Release: testing/unstable
Kernel Version: Linux paer 2.4.19-64 #1 Fri Nov 22 23:59:56 MST 2002 parisc64 unknown unknown GNU/Linux
Versions of the packages libc6 depends on:
hi libc6 2.3.1-14 GNU C Library: Shared libraries and Timezone data
Reply to: