Summary: | libsdl-1.2.8-r1 fails to emerge (-fforce-addr + volatile variables) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | André Terpstra <andre> |
Component: | [OLD] KDE | Assignee: | Gentoo Games <games> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | /proc/cpuinfo |
Description
André Terpstra
2005-03-29 00:55:43 UTC
Created attachment 54745 [details]
/proc/cpuinfo
I may be missing the point, but I included info about my CPU just to be sure
that mmx is supported
I had the same error. I believe there are 2 work-arounds. 1. disable epatch "${FILESDIR}"/${P}-gcc2.patch.bz2 #86481, or 2. filter-flags -fforce-addr Wow, thanks a lot for sharing that tip! I recompiled libsdl successfully with CFLAGS="-O3 -march=pentium4 -mtune=pentium4 -momit-leaf-frame-pointer -fomit-frame-pointer -ftracer -pipe" emerge --oneshot libsdl (I'm not an emerge expert, there may be a easier method) and am now continuing the emerge of kdemultimedia-meta. If it's not too much trouble, could someone shed some light on this, so that I may learn from it? KDE has nothing to do with libSDL... You should assign package bugs to their actual owner. It doens't matter if you're doing an "emerge kde" or "emerge some-cool-sdl-program" you would always assign to the package owner, not the owner of the package you're trying to merge... Reassigning... =] Yeah, I had the same issue. I use gcc 3.4.3 and it failed with that same error. I commented out the two gcc 2.95 patches, because they are not needed for gcc3. Anyways, filtering out a use flag because of those patches is just a hack work-around for a bad patch. The patches really needs to be excluded from the gcc3 compile. You can always move the ebuild to the portage overlay directory and comment out the two gcc2 patches, so then the changes are still there when you do a emerge sync. Slightly different Error: here, filtering -fforce-addr fixed this one as well. SDL_yuv_mmx.c: In function `ColorRGBDitherYV12MMX1X': SDL_yuv_mmx.c:113: error: can't find a register in class `GENERAL_REGS' while reloading `asm' make[3]: *** [SDL_yuv_mmx.lo] Error 1 make[3]: Leaving directory `/var/tmp/portage/libsdl-1.2.8-r1/work/SDL-1.2.8/src/video' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/libsdl-1.2.8-r1/work/SDL-1.2.8/src/video' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/libsdl-1.2.8-r1/work/SDL-1.2.8/src' make: *** [all-recursive] Error 1 -fforce-addr is now filtered for x86 This bug is reproducible on amd64, please filter it too. Please, ignore comment #8, it was a problem with the configuration of the cross compiler. |