1 |
On Mon, 2005-11-28 at 16:23 -0800, Mark Knecht wrote: |
2 |
> On another list, music based, I was told by someone that using both |
3 |
> ~x86 and ~AMD64 on the same system is incorrect by design. I have no |
4 |
> reason to not believe him but I seem to have missed this point when I |
5 |
> was building this system. |
6 |
> |
7 |
> Can someone clarify if this is the case? If so, what is the |
8 |
> recommended action for me to take at this point? |
9 |
> |
10 |
> Thanks, |
11 |
> Mark |
12 |
> |
13 |
And Tester wrote: |
14 |
> As a general rule, you should NEVER put x86 or ~x86 in your |
15 |
> ACCEPT_KEYWORDS or package.keywords on an amd64 system using an amd64 |
16 |
> profile. |
17 |
|
18 |
I completely agree with the first part of this statement but disagree |
19 |
with the second. The system wide ACCEPT_KEYWORDS should never contain |
20 |
anything x86 on an AMD64 system but I often put them into |
21 |
package.keywords. I asked almost this same question on IRC the other |
22 |
day and I'll paste the contents of that discussion here: |
23 |
|
24 |
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 |
25 |
RiverRat k, or should I always use overlays to prevent system b0rkage? |
26 |
* iluxa has quit (Remote closed the connection) |
27 |
chutzpah RiverRat: deltacow and i use ~* * in package.keywords to unmask packages all the time |
28 |
hparker I always use overlays for testing, portage.keywords for apps I will leave ~ on the system.. Just helps me keep things straight |
29 |
RiverRat chutzpah: Cool, so -m32 never makes it into the CFLAGS as a result? I would be highly annoyed if it did. |
30 |
hparker s/portage/package |
31 |
* hparker looks for his coffee cup |
32 |
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 |
33 |
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. |
34 |
chutzpah RiverRat: no problem |
35 |
jeeves http://bugs.gentoo.org/show_bug.cgi?id=113822 andrej.filipcic@×××.si->bug-wranglers@g.o, gfs ebuilds for amd64 |
36 |
RiverRat http://dev.gentoo.org/~g2boojum/portage.html <- Good info here for the people like me that are new to this stuff. |
37 |
dang RiverRat: -m32 would come from ABI, not from ACCEPT_KEYWORDS |
38 |
RiverRat Thanks, that's what I wanted to know. |
39 |
|
40 |
So, it should be fine to add them into package.keywords but stay away |
41 |
from ACCEPT_KEYWORDS with them. The real problem is programmers using |
42 |
ints to store pointers and the fact that ints are 32 bits on both |
43 |
platforms. Using longs should work on both platforms, or better yet, |
44 |
declare them as the same kind of pointer that you are using. :p There |
45 |
are other issues between the two processors (alot) but that is the most |
46 |
common problem. |
47 |
|
48 |
-- |
49 |
Tres Melton |
50 |
IRC & Gentoo: RiverRat |