1 |
ive converted my system over to x86/amd64/x32 multilib for funs. but i can |
2 |
see how some people wont want all three all the time. so the question is how |
3 |
we want to make this available to users at the release/profile level. |
4 |
|
5 |
background: x32 is a new ABI that runs on 64bit x86_64 processors. see [1]. |
6 |
you'll need gcc-4.7+, binutils-2.21.50+, glibc-2.15+, and linux-3.2+. |
7 |
|
8 |
KEYWORDS wise, i'd like to avoid having to add "x32" everywhere. instead, |
9 |
reusing "amd64". only downside is the existing USE=amd64 behavior, but we can |
10 |
address that by making MULTILIB_ABIS a USE_EXPAND (i think this came up before |
11 |
with the portage multilib discussion). |
12 |
|
13 |
release wise, we could ship a single multilib stage (x86/amd64/x32) and make |
14 |
it easy to convert to a subset. that way we still need only one. |
15 |
|
16 |
other thoughts ? |
17 |
-mike |
18 |
|
19 |
[1] https://sites.google.com/site/x32abi/ |