jeanfrancis

donjames, please post the full build.log file (using pastebin for example), as the part you posted is missing the actual error message. With this information, it will be easier to help. linuxboy, it seems your issue is a different one than donjames, I suggest you create another forum thread, as helping with both problems in the same thread will be very confusing.

This is great news! Thanks Dantrell for the hard work! :)

Thanks! :)

I only have one issue here, which seems to be only a problem while building stage3s. There is a file collision between eudev and udev-init-scripts : * Searching for /etc/init.d/udev-postmount ... sys-fs/eudev-1.5.3-r1 (/etc/init.d/udev-postmount) sys-fs/udev-init-scripts-27 (/etc/init.d/udev-postmount) It does not cause issues on a live system, but maybe because of different Portage configuration in Metro, stage3 fails with the following : * Detected file collision(s): * * /etc/init.d/udev-postmount * * Searching all installed packages for file collisions... * * Press Ctrl-C

I use multilib for Skype, wine and Steam. Steam seems to come only in 32-bit and requires multilib (at least for now).

I don't know about the long-term plans, but the new multilib approach is much more elegant (at least in theory, maybe not at ebuild level). Instead of depending on a bunch of pre-compiled emul-linux- ebuilds (which contains specific versions of a set of packages, and may be hard to maintain), multilib ebuilds can depend only on what they need, and the libraries will be built from from source for every needed architecture. Now, the transition to this may be hard. A lot of ebuilds depend on emul-linux- ebuilds, and these now start depending on native multilib ebuilds (instead of providing th