Talk:Multilib System without emul-linux Packages

GCC case
Whatever was meant in the sections "GNU Compiler Collection special case" and "Dead END" should be rephrased in an understandable and spellchecked way. I am guessing that gcc will pull additional libraries if USE=gcj is enabled and that those are not working with the 32bit approach yet. Mark (talk) 22:19, 03 October 2014.


 * I just folled this guide and had no problems so far. Luttztfz (talk) 00:41, 15 January 2015 (UTC)


 * I tend to agree with Mark. I'm left guessing as to what is meant, even though I know how to program in C.  Guess I'll figure-out myself after things break further.  What a huge mess not having "app-emulation/emul-linux-x86-baselibs app-emulation/emul-linux-x86-db app-emulation/emul-linux-x86-gtklibs app-emulation/emu -linux-x86-medialibs app-emulation/emul-linux-x86-opengl app-emulation/emul-linux-x86-qtlibs app-emulation/emul-linux-x86-soundlibs app-emulation/emul-linux-x86-xlibs" packages!  I would say it's much easier having these few packages, versus mucking around creating a mess of custom settings and custom USE profiles for abi_x86_32 just to have a default install on a 64 bit platform. No choice now as those packages are now masked. --Roger (talk) 23:51, 5 April 2015 (UTC)

no-emul-linux-x86 profile
shows a profile of the name. I selected  and followed this guide. My ACCEPT_KEYWORDS="amd64" hence stable and not testing. Selected packages are "~amd64". Everything looks good.

Shouldn't the profile be mentioned in the guide?

Luttztfz (talk) 00:40, 15 January 2015 (UTC); updated Luttztfz (talk) 00:51, 15 January 2015 (UTC)