Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 202686 Details for
Bug 283205
x11-drivers/ati-drivers-9.8 fails to build
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log for failing ati-drivers-9.8
build.log (text/plain), 5.50 KB, created by
Steven Parker
on 2009-08-30 04:52:12 UTC
(
hide
)
Description:
build.log for failing ati-drivers-9.8
Filename:
MIME Type:
Creator:
Steven Parker
Created:
2009-08-30 04:52:12 UTC
Size:
5.50 KB
patch
obsolete
> [32;01m*[0m Determining the location of the kernel source code > [32;01m*[0m Found kernel source directory: > [32;01m*[0m /usr/src/linux > [32;01m*[0m Found kernel object directory: > [32;01m*[0m /lib/modules/2.6.30-tuxonice-r5/build > [32;01m*[0m Found sources for kernel version: > [32;01m*[0m 2.6.30-tuxonice-r5 > [32;01m*[0m > [32;01m*[0m Please note that this driver supports only graphic cards based on > [32;01m*[0m r600 chipset and newer. > [32;01m*[0m This represent the ATI Radeon HD series at this moment. > [32;01m*[0m > [32;01m*[0m If your card is older then usage of x11-drivers/xf86-video-ati > [32;01m*[0m as replacement is highly recommended. Rather than staying with > [32;01m*[0m old versions of this driver. > [32;01m*[0m For migration informations please reffer to: > [32;01m*[0m http://www.gentoo.org/proj/en/desktop/x/x11/ati-migration-guide.xml > [32;01m*[0m >>>> Unpacking source... >>>> Source unpacked in /var/tmp/portage/x11-drivers/ati-drivers-9.8/work >>>> Preparing source in /var/tmp/portage/x11-drivers/ati-drivers-9.8/work ... > [32;01m*[0m Applying ati-drivers-xen.patch ... >[A[70C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying ati-powermode-opt-path-2.patch ... >[A[70C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Converting 2.6.x/Makefile to use M= instead of SUBDIRS= ... >[A[70C [34;01m[ [32;01mok[34;01m ][0m >>>> Unpacking ./../common/usr/src/ati/fglrx_sample_source.tgz to /var/tmp/portage/x11-drivers/ati-drivers-9.8/work/extra >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/x11-drivers/ati-drivers-9.8/work ... >>>> Source configured. >>>> Compiling source in /var/tmp/portage/x11-drivers/ati-drivers-9.8/work ... > [32;01m*[0m Preparing fglrx module >make -j1 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= GCC_VER_MAJ=4 KVER=2.6.30-tuxonice-r5 KDIR=/usr/src/linux kmod_build >make -C /usr/src/linux M=/var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x modules >make[1]: Entering directory `/usr/src/linux-2.6.30-tuxonice-r5' > CC [M] /var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o >In file included from include/linux/gfp.h:4, > from include/linux/kmod.h:22, > from include/linux/module.h:13, > from /var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:109: >include/linux/mmzone.h:18:26: error: linux/bounds.h: No such file or directory >include/linux/mmzone.h:256:5: warning: "MAX_NR_ZONES" is not defined >In file included from include/linux/gfp.h:4, > from include/linux/kmod.h:22, > from include/linux/module.h:13, > from /var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:109: >include/linux/mmzone.h:290: error: âMAX_NR_ZONESâ undeclared here (not in a function) >In file included from /usr/src/linux-2.6.30-tuxonice-r5/arch/x86/include/asm/pci.h:4, > from include/linux/pci.h:1098, > from /var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:116: >include/linux/mm.h:447:63: warning: "NR_PAGEFLAGS" is not defined >include/linux/mm.h:495:62: warning: "NR_PAGEFLAGS" is not defined >In file included from /var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:449: >/var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/drm_proc.h: In function âFGLDRM__vma_infoâ: >/var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/drm_proc.h:497: warning: format â%08lxâ expects type âlong unsigned intâ, but argument 5 has type âphys_addr_tâ >make[2]: *** [/var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1 >make[1]: *** [_module_/var/tmp/portage/x11-drivers/ati-drivers-9.8/work/common/lib/modules/fglrx/build_mod/2.6.x] Error 2 >make[1]: Leaving directory `/usr/src/linux-2.6.30-tuxonice-r5' >make: *** [kmod_build] Error 2 > [31;01m*[0m > [31;01m*[0m ERROR: x11-drivers/ati-drivers-9.8 failed. > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 49: Called src_compile > [31;01m*[0m environment, line 3471: Called linux-mod_src_compile > [31;01m*[0m environment, line 2678: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; > [31;01m*[0m The die message: > [31;01m*[0m Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= GCC_VER_MAJ=4 KVER=2.6.30-tuxonice-r5 KDIR=/usr/src/linux kmod_build > [31;01m*[0m > [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. > [31;01m*[0m A complete build log is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.8/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/x11-drivers/ati-drivers-9.8/temp/environment'. > [31;01m*[0m This ebuild is from an overlay named 'local': '/usr/local/portage/' > [31;01m*[0m
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 283205
: 202686