Is it possible to make an amd64 ebuild for the package sam2p? When using the x86 package, the compilation fails. There exist packages for Debian (http://packages.debian.org/unstable/graphics/sam2p) and Mandriva, so it must be possible. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Try the steps mentioned here: http://www.gentoo.org/doc/en/gentoo-amd64-faq.xml#keyword
Created attachment 72024 [details] emerge output (both stdout and stderr) for sam2p-0.44 Adding "=media-gfx/sam2p-0.44 x86" to package.keywords was what I had done. I shoud've included my emerge output immediately. Better late than never.
What gcc version are you using? I don't believe this error is hardware specific. Using x86 hardware it fails for me as well. The package seems to only be compatible with gcc 3.3.x, failing with the same error for gcc 3.4.x and 4.0.x Thus I think sam2p needs to be fixed to compile with newer versions of gcc Perhaps this issue should be raised in severity and inclusive of all architectures?
(In reply to comment #3) > What gcc version are you using? > 3.4.4-r1, latest stable for amd64 > I don't believe this error is hardware specific. > Might be. I can't easily check this (x86 would be possible if it is really necessary to check this). > Perhaps this issue should be raised in severity and inclusive of all > architectures? > If it fails on x86 as well, definitely. Maybe the summary should then also be changed? I don't know if this my call or the bug owner?
(In reply to comment #4) > > What gcc version are you using? > > > 3.4.4-r1, latest stable for amd64 > Might be. I can't easily check this (x86 would be possible if it is really > necessary to check this). I use x86 and it does fail on x86 like I said with gcc3.4.x and higher. And since you had a problem compiling using gcc3.4.x I feel justified in assuming that the problem is related to gcc and not architecture. (if you want to use it in the meantime, installing a version of gcc3.3.x is an option, as it would install in a different slot and then you just tell which version to use through gcc-config and use 3.3.x for sam2p and then switch back to 3.4.x) > If it fails on x86 as well, definitely. Maybe the summary should then also be > changed? I don't know if this my call or the bug owner? > since you are the reporter, I would assume that it'd be okay to change details of the bug to more accurately report the issue.
Changed summary, hardware and severity to reflect current knowledge about the issue.
I have the same problem emerging sam2p with gcc-3.4.6-r1. But I correctly compiled it by hand (following the very simple instructions from the author) in the same system where I tried to emerge. So may it be an ebuild problem ?
I increased the severity of this bug after asking around and finding nobody who could (still) emerge sam2p.
Last severity change reversed.
Just added 0.45 to portage which should fix the compilation issues. Download from sam2p-0.45.tar.bz2 from http://dev.gentoo.org/~twp/distfiles/sam2p-0.45.tar.bz2 if it doesn't download automatically. The author refuses to distribute version-stamped tarballs so we have to mirror them for Gentoo, and it can take a while for these to propagate. Re-open this bug if problems persist. Cheers, Tom
For me, the .45 version works fine. However, others still stumble upon this bug because the non-emerging .44 version is marked as stable. I advise removing or hard-masking the .44 version and possibly leaving the .45 version as ~, as it seems the package is not used alot and thus not well tested.
*** This bug has been marked as a duplicate of bug 154787 ***
