Compile error in xc/programs/Xserver/fb/fbmmx.c if mmx is in USE flags. The fix is present in Xorg CVS. Reproducible: Always Steps to Reproduce:
Created attachment 50313 [details, diff] fbmmx-gcc4-compile-fix.patch This fixes at least compilation, don't know whether it works run-time.
i had to also apply 2 patchs from this bug: https://bugs.freedesktop.org/show_bug.cgi?id=2008 to get it to compile it still isnt working tho as the fbmmx seems to add some symbols and then has a linking problem ill attach the 2 patchs i had to extract from the bug to save someone else some time so they can get the link error if they want to play with that
Created attachment 50407 [details, diff] cfbgc-gcc4.patch
Created attachment 50408 [details, diff] radeon-gcc4.patch
Patch for xorg-x11 is already available, no need for gcc-porting to be on here.
First problem still exists with current ebuild in portage.
ajax, I know you've tested with gcc4. Which of these are needed, correct, etc?
I needed at least the fbmmx-gcc4-compile-fix.patch and cfbgc-gcc4.patch in order to compile, but I didn't have time to finish the whole build so third one may be possibly needed.
Created attachment 51031 [details, diff] MMX GCC4 compile fix I got the same linking errors with MMX that Bret got. I checked out a copy of Xorg from cvs and I backported the changes for the MMX fb code that occurred after the MMX patch got applied that we were using. It allowed me to successfully compile Xorg in my chroot. I can't attest to it working yet, so please test it. For GCC 4, all 3 patches are needed to get it to compile.
i just tried these patchs and now it compiles and works fine for me using ati-drivers btw Portage 2.0.51.16 (default-linux/x86/2004.2/gcc34, gcc-4.0.0, glibc-2.3.4.20050125-r0, 2.6.10-bk3 i686) ================================================================= System uname: 2.6.10-bk3 i686 AMD K7 processo Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 11 2005, 19:38:23)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks fixpackages sandbox sfperms" GENTOO_MIRRORS="http://gentoo.llarian.net/ http://gentoo.binarycompass.org http://mirror.datapipe.net/gentoo http://gentoo.eliteitminds.com" LANG="en_US.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -Wl,-z,combreloc -Wl,-z,nocopyreloc" MAKEOPTS="" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/mdhd/portage.local" SYNC="rsync://vox.net/gentoo-portage" USE="x86 3dnow 3dnowex X alsa apm avi berkdb bitmap-fonts cjk crypt curl dga dvdvd dvdread encode f77 fam fbcon fbdev flac foomaticdb fortran gdbm gif gtk gtk2 imagemagick imlib ipv6 jpeg libg++ libwww live mad matroska mikmod mmx mmx2 motif mp3 mpeg ncurses nls nptl oggvorbis opengl pam pdflib perl png pvm python quicktime readline real samba sdl slang spell sse ssl svga tcltk tcpd theora tiff truetype truetype-fonts type1-fonts userlocales v4l v4l2 xml xml2 xmms xprint xvzlib" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL
*** Bug 81713 has been marked as a duplicate of this bug. ***
all of these are "needed" in some sense. the fbmmx one is sort of an accidental fix, but i'm glad to see it works. they should all be safe to apply.
How did this managed to get marked as criticial gentoo doesnt even support gcc 4 as of yet read /usr/portage/profile/package.mask. All bugs need to be upstreamed to there respective parties not gentoo.
Jory, spyderous raised the severity on this bug, and xorg is his package, so I am assuming he would like to see this issue resolved. The bugs are fixed upstream, and patches are supplied, which is what was asked for. What was said was not to file bugs without patches. If we start working on patching programs now, hopefully we will have an easier time supporting GCC4 when it does come out. All of these patches probably aren't going to be applied immediately by upstream.
Should be fixed in 6.8.2-r2.
