Bug 193107 - games-fps/quake2-icculus build error with sanitized kernel headers (no asm/io.h)
|
Bug#:
193107
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P3
|
|
Resolution: FIXED
|
Assigned To: games@gentoo.org
|
Reported By: timofonic@gmail.com
|
|
Component: Games
|
|
|
URL:
|
|
Summary: games-fps/quake2-icculus build error with sanitized kernel headers (no asm/io.h)
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2007-09-19 18:28 0000
|
games-fps/quake2-icculus has problems for building. Here I will attach two
files, one containing the build error and other being a paludis --info output.
paludis 0.24.6
Built by paludisbuild@localhost on 2007-09-18T20:02:52+0200
CXX: i686-pc-linux-gnu-g++ 4.1.2 (Gentoo 4.1.2 p1.0.1)
CXXFLAGS: -march=athlon-xp -O2 -pipe -fomit-frame-pointer
LDFLAGS:
DATADIR: /usr/share
LIBDIR: /usr/lib
LIBEXECDIR: /usr/libexec
SYSCONFDIR: /etc
stdlib: GNU libstdc++ 20070214
libebt: 1.3.0
libwrapiter: 1.0.0
sandbox: enabled
Repository virtuals:
Configuration information:
format: virtuals
Repository installed_virtuals:
Configuration information:
format: installed_virtuals
Repository gentoo:
Configuration information:
buildroot: /mnt/tmp/vartmp/paludis
cache: /usr/portage/metadata/cache
distdir: /usr/portage/distfiles
eclassdirs: /usr/portage/eclass
format: ebuild
location: /usr/portage
names_cache: /usr/portage/.cache/names
newsdir: /usr/portage/metadata/news
pkgdir: /usr/portage/packages
profiles: /usr/portage/profiles/default-linux/x86/2007.0
securitydir: /usr/portage/metadata/glsa
setsdir: /usr/portage/sets
sync: rsync://rsync.europe.gentoo.org/gentoo-portage
sync_options:
write_cache: /var/cache/paludis/metadata
Package information:
app-admin/eselect-compiler: (none)
app-shells/bash: 3.2_p17
dev-java/java-config: (none)
dev-lang/python: 2.4.4-r4
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache: 2.4-r7
dev-util/confcache: (none)
sys-apps/baselayout: 1.12.9-r2
sys-apps/sandbox: 1.2.17
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3,
1.9.6-r2, 1.10
sys-devel/binutils: 2.17-r1
sys-devel/gcc-config: 1.3.16
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.21
Variable information:
ACCEPT_KEYWORDS:
CBUILD: i686-pc-linux-gnu
CFLAGS: -march=athlon-xp -O2 -pipe -fomit-frame-pointer
CHOST: i686-pc-linux-gnu
CONFIG_PROTECT:
CONFIG_PROTECT_MASK:
CTARGET:
CXXFLAGS: -march=athlon-xp -O2 -pipe -fomit-frame-pointer
DISTDIR: /usr/portage/distfiles
FEATURES:
GENTOO_MIRRORS:
INSTALL_MASK:
LANG:
LC_ALL:
LDFLAGS:
LINGUAS:
MAKEOPTS: -j2
PORTAGE_COMPRESS:
PORTAGE_COMPRESS_FLAGS:
PORTAGE_RSYNC_EXTRA_OPTS:
PORTAGE_RSYNC_OPTS:
PORTAGE_TMPDIR: /mnt/tmp/vartmp/paludis
PORTDIR: /usr/portage
PORTDIR_OVERLAY:
SYNC:
USE:
Repository installed:
Configuration information:
buildroot: /mnt/tmp/vartmp/paludis
format: vdb
location: /var/db/pkg
names_cache: /var/db/pkg/.cache/names
provides_cache: /var/db/pkg/.cache/provides
root: /
world: /var/db/pkg/world
can you make a symlink from /usr/src/linux/include/asm-i386/ to
/usr/src/linux/include/asm?
i.e. "ln -s /usr/src/linux/include/asm-i386 /usr/src/linux/include/asm"
(Assuming "linux" is a symlink pointing to the kernel source tree you're using)
It looks like it may be having an issue finding this directory, a lot this
possibly having to do with what kernel version you're using.
Try that and post your result.
Hey, I just ran into this, too. It definitely does seem related to
sys-kernel/linux-headers. I symlinked the one file, io.h, and tried a
recompile, but then it just complained about missing linux/string.h and
linux/compiler.h (which were included from asm/io.h), and I didn't feel like
heading down the recursively-symlink road. Besides, stuff in /usr/src/linux
really shouldn't live outside of there, anyway.
Dunno what can be done about it, though - I suspect this is something that'd
have to end up going upstream or something.
Oh, I forgot to mention that I'm currently on
sys-kernel/linux-headers-2.6.23-r3
One easy fix, btw, seems to be to just disable the "aalib" USE flag, since
that's where this error's getting generated. Seeing as though that's a pretty
superfluous flag, anyway, that shouldn't be a big deal for anyone.
