| 1 |
On Thursday 08 December 2011 16:40:58 Markos Chandras wrote: |
| 2 |
> On 12/08/2011 09:34 PM, Mike Frysinger wrote: |
| 3 |
> > On Thursday 08 December 2011 16:29:15 Markos Chandras wrote: |
| 4 |
> >> On 12/08/2011 09:22 PM, Mike Frysinger wrote: |
| 5 |
> >>> the releases will include all 3 ABIs (which only affects |
| 6 |
> >>> gcc/glibc in terms of overhead). if people want to use x32 |
| 7 |
> >>> with less other ABIs, then i think the expected use case will |
| 8 |
> >>> be for them to set MULTILIB_ABIS in their make.conf: |
| 9 |
> >>> /etc/make.conf:MULTILIB_ABIS="x32" |
| 10 |
> >> |
| 11 |
> >> What happens if all three ABIS are set in MULTILIB_ABIS? What |
| 12 |
> >> would be the default ABI for compiled binaries? |
| 13 |
> > |
| 14 |
> > default ABI is controlled by $DEFAULT_ABI. the order of |
| 15 |
> > $MULTILIB_ABIS does not matter anywhere. |
| 16 |
> |
| 17 |
> Doh! Right I forgot. I guess we need to create a quick draft and put |
| 18 |
> it in amd64 project page. At least the MULTILIB_ABIS variable may be |
| 19 |
> useful for people who want to try that or a quick HowTo on how to live |
| 20 |
> migrate from amd64 to x32 ABIS and vice versa. |
| 21 |
|
| 22 |
i want to hold off on that until i commit biarch support, and then verify the |
| 23 |
upgrade path actually works :) |
| 24 |
-mike |
Archives