| View previous topic :: View next topic |
| Author |
Message |
robinmarlow
Apprentice
Joined: 10 Mar 2004
Posts: 167
|
 Posted: Mon Sep 09, 2013 11:07 am Post subject: ABI_X86 query.... |
 |
|
I have been trying to get my head around this ABI_X86 setting.
On various threads I saw the solution was to put:
in make.conf, but I found I ended up in a mess of blockers.
By putting in instead it all worked..... until I tried to do 32bit prefix in wine which obviously was now not possible.
I found by now changing to ABI_X86="32 64" wine would compile with both 32bit as well but emerge -ND world suggests >100 packages to rebuild.
So my question is do I have to set ABI to 32 globally in make.conf and live with the big rebuild or can I just do it for certain packages in package.use?
Surely most stuff doesn't need to be 32bit?
Robin |
|
| Back to top |
|
 |
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Mon Sep 09, 2013 8:40 pm Post subject: |
|
|
It is my understanding that ABI_X86 can be set in make.conf as follows:
when using a multilib profile. I am successfully running a 32 bit only wine install to play both Eve Online and Rift.
The multilib use variable should supersede the ABI_X86 Variable. Notice that wine no longer has a multilib USE Flag:
Gentoo Wiki:Wine, and that win32 and win64 have been replaced by the ABI_X86 variable in >=wine-1.6
For info on how to manually create a 32 bit Prefix in a 64 bit wine see:7.2. How do I create a 32 bit wineprefix on a 64 bit system?
I did it the way described in the FAQ until i used the ABI_x86 setting...
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper |
|
| Back to top |
|
|
robinmarlow
Apprentice
Joined: 10 Mar 2004
Posts: 167
|
| Posted: Mon Sep 09, 2013 9:46 pm Post subject: |
|
|
That is interesting - I hadn't realised you could build wine without the 64bit environment.
it appears that I can have:
make.conf: ABI_X86="64" (b.cos I want a 64 bit system overall)
package.use: app-emulation/wine abi_x86_32 -abi_x86_64
and everything seems happy.
Or is this fundamentally wrong and I'm heading for a fall?
Robin |
|
| Back to top |
|
|
eyoung100
Veteran
Joined: 23 Jan 2004
Posts: 1428
|
| Posted: Mon Sep 09, 2013 10:10 pm Post subject: |
|
|
| robinmarlow wrote: | That is interesting - I hadn't realised you could build wine without the 64bit environment.
it appears that I can have:
make.conf: ABI_X86="64" (b.cos I want a 64 bit system overall)
package.use: app-emulation/wine abi_x86_32 -abi_x86_64
and everything seems happy.
Or is this fundamentally wrong and I'm heading for a fall?
Robin |
Before you jump of the deep end for pure 64-Bit read abi_x86_32 Multilib madness [Not as SOLVED as I thought], because as I said the multilib profile is the parent of this variable, due to inheritence. Example:
| Code: | | eselect profile set <some value besides no-multilib> |
sets the multilib flag. Don't confuse multilib and the abi. In my case I have a multilib system and a 32 bit abi, so that all the multimedia stuff in KDE like VLC will work. This variable was added by a developer to attempt to build a multilib system without the need for packages in the emul-linux/* category, which the developer still hasn't done because there is no way to solve the "chicken or egg issue"
_________________
The Birth and Growth of Science is the Death and Atrophy of Art -- Unknown
Registerd Linux User #363735
Adopt a Post | Strip Comments| Emerge Wrapper |
|
| Back to top |
|
|
|
Portage & Programming
