On Sat, 2015-02-21 at 19:35 -0500, jonathan ferguson wrote:
> Package: linux-kbuild-3.16
> Version: 3.16-3
> Severity: important
> Tags: lfs
>
> Dear Maintainer,
>
>
> * What led up to the situation?
>
>
> I am running Debian Jessie, Linux debian 3.16.0-4-amd64 #1 SMP Debian
> 3.16.7-ckt2-1 (2014-12-08) x86_64 GNU/Linux. I attempted to install fglrx and
> discovered that ALL dkms kernel module builds were failing for me with: "Value
> too large for defined data type"
>
> I have a ~4TB XFS filesystem... According to XFS documentation, by
> default for any FS over 2GB, the filesystem is created to support 64 bit
> inodes.
I don't know what documentation you're looking at, but mkfs.xfs(8) says
"In the default inode allocation mode, inode blocks are chosen such that
inode numbers will not exceed 32 bits, ..."
You are likely to see many other 32-bit programs failing because they
don't need to work with large files and no-one thought about large inode
numbers.
[...]
> This looks like a regression of the linux-kbuild tools for kernel 3.16.
I don't think so.
[....]
> Of the large number of linux-headers-common and linux-kbuild
> trees on my system there are only a few files using 32-bit stat() family
> interface only, and only in linux-kbuild-3.16:
>
>
> user@debian:src$ summarise_stat.pl linux-kbuild-3.16/
> Summary by status
> -----------------
> 29 69.0% are scripts (shell, perl, whatever)
> 6 14.3% don't use any stat() family calls at all
> 7 16.7% use 32-bit stat() family interfaces only [BROKEN]
> 7 16.7% BROKEN
[...]
You have installed linux-kbuild-3.16:i386 and not
linux-kbuild-3.16:amd64; this might be indirectly due to the
recommendations of dkms.
Of course, we should build with _FILE_OFFSET_BITS=64 on 32-bit
architectures.
Ben.
--
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
- Albert Einstein
Attachment:
signature.asc
Description: This is a digitally signed message part