Bug#391305: marked as done (linux-kernel-headers: FTBFS on arm - complains about __32 t; in include/asm/byteorder.h:21)
Your message dated Sat, 07 Oct 2006 06:33:26 -0700
with message-id <E1GWCIw-0003IH-Nv@spohr.debian.org>
and subject line Bug#391305: fixed in linux-kernel-headers 2.6.18-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-kernel-headers
Version: 2.6.18-2
Severity: serious
Justification: no longer builds from source
building fails with
cc -Wall -Werror -W -I /root/linux-kernel-headers-2.6.18/testsuite/../debian/linux-kernel-headers/usr/include
-I /root/linux-kernel-headers-2.6.18/testsuite/../include -ansi -pedantic -o ansi-msdos-fs.o -c msdos-fs.c
In file included from /root/linux-kernel-headers-2.6.18/testsuite/../include/linux/msdos_fs.h:7,
from msdos-fs.c:1:
/root/linux-kernel-headers-2.6.18/testsuite/../debian/linux-kernel-headers/usr/include/asm/byteorder.h:21:
error: expected '=', ',', ';', 'asm' or '__attribute__' before '__u32'
cc1: warnings being treated as errors
In file included from /root/linux-kernel-headers-2.6.18/testsuite/../include/linux/byteorder/little_endian.h:12,
from /root/linux-kernel-headers-2.6.18/testsuite/../debian/linux-kernel-headers/usr/include/asm/byteorder.h:54,
from /root/linux-kernel-headers-2.6.18/testsuite/../include/linux/msdos_fs.h:7,
from msdos-fs.c:1:
/root/linux-kernel-headers-2.6.18/testsuite/../include/linux/byteorder/swab.h: In function '__fswab32':
/root/linux-kernel-headers-2.6.18/testsuite/../include/linux/byteorder/swab.h:148:
warning: implicit declaration of function '___arch__swab32'
make[1]: *** [ansi-msdos-fs.o] Error 1
make[1]: Leaving directory /root/linux-kernel-headers-2.6.18/testsuite'
make: *** [lkh-test] Error 2
This is as reported in
http://buildd.debian.org/fetch.php?pkg=linux-kernel-headers&arch=arm&ver=2.6.18-1&stamp=1159121860&file=log
and confirmed on leisner.d.o
This seems a bit wierd:
/root/linux-kernel-headers-2.6.18/testsuite/../include/linux/byteorder/little_endian.h:12
leisner:~/linux-kernel-headers-2.6.18/testsuite# grep -n "#include" ../include/linux/byteorder/little_endian.h
11:#include <linux/types.h>
12:#include <linux/byteorder/swab.h>
which is including linux/byteorder/swab.h, not asm/byteorder.h. so how did we get to the error in asm/byteorder.h:21 ?
using -E instead of -c in above command we get:
the source:
-------------------asm-arm/byteorder.h----------
#ifndef __ASM_ARM_BYTEORDER_H
#define __ASM_ARM_BYTEORDER_H
#include <linux/compiler.h>
#include <asm/types.h>
static inline __attribute_const__ __u32 ___arch__swab32(__u32 x)
{
__u32 t;
#ifndef __thumb__
if (!__builtin_constant_p(x)) {
----------------------------------
preprocessed to:
---------------------------------
typedef __signed__ int __s32;
typedef unsigned int __u32;
__extension__ typedef __signed__ long long __s64;
__extension__ typedef unsigned long long __u64;
# 20 "/root/linux-kernel-headers-2.6.18/testsuite/../debian/linux-kernel-headers/usr/include/asm
/byteorder.h" 2
static inline __u32 ___arch__swab32(__u32 x)
{
__u32 t;
if (!__builtin_constant_p(x)) {
--------------------------------------
which looks OK to me.
(Is __attribute_const__ supposed to be null?)
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm (armv4tl)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-csb637
Locale: LANG="", LC_CTYPE=""
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux-kernel-headers
Source-Version: 2.6.18-2
We believe that the bug you reported is fixed in the latest version of
linux-kernel-headers, which is due to be installed in the Debian FTP archive:
linux-kernel-headers_2.6.18-2.diff.gz
to pool/main/l/linux-kernel-headers/linux-kernel-headers_2.6.18-2.diff.gz
linux-kernel-headers_2.6.18-2.dsc
to pool/main/l/linux-kernel-headers/linux-kernel-headers_2.6.18-2.dsc
linux-kernel-headers_2.6.18-2_sparc.deb
to pool/main/l/linux-kernel-headers/linux-kernel-headers_2.6.18-2_sparc.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 391305@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Clint Adams <schizo@debian.org> (supplier of updated linux-kernel-headers package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 7 Oct 2006 08:59:27 -0400
Source: linux-kernel-headers
Binary: linux-kernel-headers
Architecture: source sparc
Version: 2.6.18-2
Distribution: unstable
Urgency: high
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Changed-By: Clint Adams <schizo@debian.org>
Description:
linux-kernel-headers - Linux Kernel Headers for development
Closes: 391305
Changes:
linux-kernel-headers (2.6.18-2) unstable; urgency=high
.
* Update byteorder-const.patch with patch from Wookey,
fixing arm FTBFS. closes: #391305.
Files:
db6b3bf5874ada7ed8a1e5b317fd42b9 881 devel standard linux-kernel-headers_2.6.18-2.dsc
905ac12fd2e2b51384f2b32b8fa7b56b 22679 devel standard linux-kernel-headers_2.6.18-2.diff.gz
e65a99938f1474f7ec64ccade6c602cd 1857250 devel standard linux-kernel-headers_2.6.18-2_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Debian!
iD8DBQFFJ6jL5m0u66uWM3ARAsSQAKCukfAHY+YDB3cRI1JWsNXC2X1qOACfS3pv
x6REF7AuXVHFIo05Hp7iO70=
=y0qm
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: