On Mon, 2005-11-28 at 16:23 -0800, Mark Knecht wrote: > On another list, music based, I was told by someone that using both > ~x86 and ~AMD64 on the same system is incorrect by design. I have no > reason to not believe him but I seem to have missed this point when I > was building this system. > > Can someone clarify if this is the case? If so, what is the > recommended action for me to take at this point? > > Thanks, > Mark > And Tester wrote: > As a general rule, you should NEVER put x86 or ~x86 in your > ACCEPT_KEYWORDS or package.keywords on an amd64 system using an amd64 > profile.
I completely agree with the first part of this statement but disagree with the second. The system wide ACCEPT_KEYWORDS should never contain anything x86 on an AMD64 system but I often put them into package.keywords. I asked almost this same question on IRC the other day and I'll paste the contents of that discussion here: RiverRat Question: Does the ACCEPT_KEYWORDS value ever get interpretted for anything other than to see if a package can be installed via masking. In other words, if I add ~x86 to something on my amd64 will that ever make it to compile flags or anything like that? I've done that for perl/python scripts as I know the interrupter was compiled correctly but I'm leary of adding it to binary files. It is just for testing and temporary use but is that o RiverRat k, or should I always use overlays to prevent system b0rkage? * iluxa has quit (Remote closed the connection) chutzpah RiverRat: deltacow and i use ~* * in package.keywords to unmask packages all the time hparker I always use overlays for testing, portage.keywords for apps I will leave ~ on the system.. Just helps me keep things straight RiverRat chutzpah: Cool, so -m32 never makes it into the CFLAGS as a result? I would be highly annoyed if it did. hparker s/portage/package * hparker looks for his coffee cup chutzpah RiverRat: never has for me... putting append-flags -m32 in any package except for something like grub would be a somewhat dumb thing to do RiverRat chutzpah: I agree, I just haven't dug through the portage code enough to make a definitive staement about it. Thanks for the info. chutzpah RiverRat: no problem jeeves http://bugs.gentoo.org/show_bug.cgi?id=113822 [EMAIL PROTECTED]>[EMAIL PROTECTED], gfs ebuilds for amd64 RiverRat http://dev.gentoo.org/~g2boojum/portage.html <- Good info here for the people like me that are new to this stuff. dang RiverRat: -m32 would come from ABI, not from ACCEPT_KEYWORDS RiverRat Thanks, that's what I wanted to know. So, it should be fine to add them into package.keywords but stay away from ACCEPT_KEYWORDS with them. The real problem is programmers using ints to store pointers and the fact that ints are 32 bits on both platforms. Using longs should work on both platforms, or better yet, declare them as the same kind of pointer that you are using. :p There are other issues between the two processors (alot) but that is the most common problem. -- Tres Melton IRC & Gentoo: RiverRat
signature.asc
Description: This is a digitally signed message part
