Anders Kaseorg <[EMAIL PROTECTED]> writes: > Package: openafs-modules-source > Version: 1.4.5~pre2.dfsg1-1
> The openafs module does not build on an i386 userspace with an amd64 > kernel, because the debian/module/sysname script uses `dpkg > --print-architecture` to compute the sysname to pass to configure, which > returns the architecture of the userspace instead of the kerenel. > # m-a -t build openafs > … > sh configure --with-afs-sysname=i386_linux26 \ > … > /usr/src/modules/openafs/src/libafs/MODLOAD-2.6.18-5-amd64-MP/afs_vnop_flock.c:46: > error: conflicting types for ‘lockIdSet’ > The module builds and works fine if I somehow force it to configure > --with-afs-sysname=amd64_linux26, for example: > # MAKEFLAGS=SYS_NAME=amd64_linux26 m-a -t build openafs > This should be detected automatically. I don't consider this to be a configuration that's a high priority to support more than is currently available, but I'm certainly willing to do so if there's some way to do so. However, I don't know how to go about doing that short of parsing uname, which isn't something that I know how to test on all of the architectures that OpenAFS supports (plus, I don't know if it would work properly for all of them). Tested patches welcome. I will document the workaround in README.modules in the next release until there's a better fix. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
