j-g-

eselect profile was removed on funtoo, so that wiki page is outadated, and there is no way to use overlay profiles with epro(The script assumes you only  want profiles from $PORTDIR),  but actually manually putting togheter the profile isn't hard, just take a look at /etc/portage/make.profile/parent, and edit the file, is pretty obvious. I'm trying to get epro to read overlay profiles, but I've been too lazy these days, and only got the start of it.

It is not on the tree, but the upstream git page has instructions for installation in gentoo(you can apply those to funtoo) from a greek overlay, but you'll need to learn about layman and overlays (non official repos), package.accept_keywords and live ebuilds(versions 9999* basically fresh from git). start by installing layman also you should check eix(emerge eix) to search for packages, nobody really uses emerge --search(too slow).

If you will try to install it, I advice you, when using overlays, be aware the quality of the ebuilds might not be as good as the main repo, the ebuilds might be unmaintained. But that shouldn't stop you, just check the overlay is being maintained, and if you use live ebuilds, that means you can report any problem you have directly to upstream because you are building their latest code.

No make.conf changes, I explained to you about this message from portage in your previous topic, also check that suggested manpage. get used to that kind of output, if you  read it carefully as recommended, you'll find the instructions there.
Also this is important as you are building a desktop:
http://www.funtoo.org/News:ABI_X86_64_and_32(This type of info, used to be in news that came with the portage tree, but in funtoo, IMO, the bad decision of removing these from the tree, and put them in the webpage was made. in gentoo emerge notifies you there are important news to know about, like this one)

Did you re-run  the ebuild command 2 times from inside /var/tmp/portage/... the directories created get remove everytime you try to do a new build either using emerge  or ebuild ... clean, I have had similar errors when I forgot to cd out of the autogenerated directories.
 
Now that you have identified that the failure is in speex, report a bug so the dependecy get's added to the ebuild so this error doesn't happen to other people.
 
Since you emerged it with one-shot you shouldn't have any problems once it gets fixed. you can try from your home dir, to check the errors are because of what I tell you before.
$ sudo emerge --oneshot pulseaudio

See eclean-dist --help , it has many useful options.

So far my experience has been, you can use /usr/local/portage, or an overlay of your own, I would recommend the overlay, since you can make changes to it as normal user. there's an skeleton overlay uploaded for funtoo in github, you can start from that.
 
Make the directory structure for the package you wan to test in your overlay dir:

$ mkdir -p ${OVERLAY_DIR}/cat/pkg/ # Edit your ebuild: $ $EDITOR ${OVERLAY_DIR}/cat/pkg/pkg-0.0.ebuild # generate a Manifest $ ebuild ${OVERLAY_DIR}/cat/pkg/pkg-0.0.ebuild manifest Add your overlay via making a overlay.xml file in /etc/layman/overlays/ (this is documented in the layman manual) or adding to your make.conf
PORTDIR_OVERLAY="${PORTDIR_OVERLAY} $YOUR_OVERLAY_DIR" If you don't have the package installed already or are adding new dependencies you can do:
$ sudo emerge --onlydeps '=cat/pkg-0.0' and then you can test your ebuild step by step using the 'ebuild' command, I try before merging anything I edit, generating a package, this means all the build process is made except actually getting the package in your filesystem, you can inspect the tarball generated to see everything looks right and then merge.
$ sudo ebuild ${OVERLAY_DIR}/cat/pkg/pkg-0.0.ebuild package That said you should read first and mainly refer to the gentoo dev documentation.[1] or 'emerge -av devmanual' 
[1] http://devmanual.gentoo.org/index.html

If you crafted that manually you missed adding the initrd command to load your dracut generated initramfs, and since you are using dracut you might want to explore more of its options, you can set your kernel command line in /etc/dracut.conf, and other ineresting things, this will make the upgrading kernel process more cleaner since you don't need to add the command line every time, also make sure you have ' hostonly="yes" ' in dracut.conf.

This is really weird, try to see if udev report any error, run as root 'udevadm monitor' and plug the device, and watch the contents of /proc/net/dev and /proc/net/wireless, I don't think the problem is the kernel, but can try using sys-kernel/gentoo-sources, and use iwconfig from wireless-tools, and ip from iproute2, instead of ifconfig, there might be a bug that's causing this, in which case I can only help you find out what is causing it, it's up to you to report it to the proper people.