1 |
Mike Frysinger schrieb: |
2 |
> On Friday, September 16, 2011 04:28:24 Stratos Psomadakis wrote: |
3 |
>> Is a x86/amd64/x32 multilib profile just going to provide toolchain |
4 |
>> support for x32 binaries (like x86 in a x86/amd64 multilib profile), or |
5 |
>> do we want a 'full' x32 profile, where every package is built by default |
6 |
>> as x32 code? |
7 |
> |
8 |
> this is an issue for the multilib-portage project |
9 |
> -mike |
10 |
|
11 |
How is this an issue for multilib-portage? It only requires a toolchain able to build for the target |
12 |
and the details in environment (like possible targets and needed additional flags for each target). |
13 |
Thinking about the issues when starting with a new target, it might be a good idea to have the basic |
14 |
system (stage3) for the multilib profile to contain files for all targets, but only enable the |
15 |
default ABI. So when a user wants some other targets, he already has a base system, else he can just |
16 |
reinstall the base system and drop the unused files with this step. |