| View previous topic :: View next topic |
| Author |
Message |
Fran
Guru
Joined: 29 Feb 2004
Posts: 530
Location: Coruña (Spain)
|
 Posted: Sun Feb 24, 2013 9:33 am Post subject: multilib vs no-multilib+chroot |
 |
|
I was looking for a way to get a 32bit qtcurve working on my system to beautify skype when I realized that, on the one hand, I had a minimal set of packages carefully set up in /usr/lib64 and, on the other, 6 or 7 giant-binary-blobs-of-hell that basically defeat the purpose or using gentoo.
So I switched to no-multilib, set up a 32bit chroot and voilà, everything works as it should, I can choose what I install - I have my qtcurve for Skype  - and I have updated packages for what I need (mesa). I don't see any disadvantage over multilib (1 extra GB, but who cares).
Are there plans to replace the emul-linux packages for something else? To me, they seem... out of place in gentoo. Maybe putting the multilib overlay in the main tree in the future? |
|
| Back to top |
|
 |
Genone
Retired Dev
Joined: 14 Mar 2003
Posts: 9523
Location: beyond the rim
|
| Posted: Mon Feb 25, 2013 1:57 pm Post subject: |
|
|
| There have been plans to replace the binary multilib packages for years, wether they will actually be implemented and released as default one day is another question. |
|
| Back to top |
|
|
grey_dot
Tux's lil' helper
Joined: 15 Jul 2012
Posts: 142
|
| Posted: Tue Feb 26, 2013 12:31 am Post subject: |
|
|
| There's a third option. You could use crossdev to build i686 sysroot, and then use cross-emerge for everything you need. Works fine for me. |
|
| Back to top |
|
|
_______0
Guru
Joined: 15 Oct 2012
Posts: 521
|
| Posted: Sat Mar 02, 2013 7:52 pm Post subject: |
|
|
would be neat an automated way, tweakable afterwards, of x32 chroot in non-multilib. By means of a USE flag switch or an option in make.conf.
Some things are confusing such as the mixed role of /dev/shm and many graphics cards packages in chroot. |
|
| Back to top |
|
|
_______0
Guru
Joined: 15 Oct 2012
Posts: 521
|
| Posted: Sat Mar 02, 2013 7:54 pm Post subject: |
|
|
| grey_dot wrote: | | There's a third option. You could use crossdev to build i686 sysroot, and then use cross-emerge for everything you need. Works fine for me. |
I find your idea intriguing. Would this forgo the need to install emerge portage and all that in chroot? How't'd work? By compiling in host then copying to chroot??
thnks |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54216
Location: 56N 3W
|
| Posted: Sat Mar 02, 2013 8:20 pm Post subject: |
|
|
_______0,
Install crossdev, use it to build a sysroot of your choice, then play with it.
I use it for ARM (for Raspberry Pi) on amd64, so cannot chroot into it :) but if you make a 32bit install, it will justwork.
You can share /usr/portage and /usr/portage/distfiles but not /usr/portage/packages.
In theory, you can run | Code: | | emerge-wrapper --init |
then emerge stuff into your cross root but not everything plays nicely there.
Still, you will have more success with x86 on amd64, since x86 code will run on an amd64.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Gentoo Chat
