Now running the updated 1.1.25 version of wine, Digsby installed without a problem. I started it up, logged in and now its running just fine. The only issue I've noticed at all with Digsby under Wine is the fact that the text input box in chats seems to wrap text after a few words. Its annoying when writing a long reply to someone, but nothing more than just annoying. It doesn't cause any problems or crash anything, so its just an annoyance at this point.

Hopefully this helps someone with Digsby under Linux. I love using it as my IM client, but I can't wait until they get their Linux version going.

Once I got VMWare Player installed, I ran into a few issues. My first issue was that it was unable to find a specific symbol... this was in relation to recompiling dev-cpp/gtkmm with the use flag "accessibility". Once that is rebuilt you also need to rebuild x11-libs/libsexy, dev-cpp/libsexymm and x11-libs/libview. Once those are rebuilt, the error about the missing symbol went away, then it was on to a whole new error message.

The next error message seems to come only when dbus is enabled

process 29624: Attempt to remove filter function 0x7f481078f444 user data 0x7a5490, but no such filter has been added
D-Bus not built with -rdynamic so unable to print a backtrace

Now I searched far and wide for this, and the only solution I found for a while was just to disable dbus completely. I didn't want to do this because I've got a few programs that are using dbus. After searching more, I found something else. Finally, a Gentoo Bug that tells me what's wrong! It appears by the bug report that if you have dbus running, you must also have hald running. Once I started up hald, vmplayer has worked perfectly.

Hopefully this will help someone and save them from pulling their hair out unlike I did.

When you first emerge ccache, it automatically creates symlinks to itself for your CHOST setting. That means that in /usr/lib/ccache/bin I had i686-pc-linux-gnu-gcc symlinks to ccache. That's why compiles were failing, the compiler didn't exist on my system, but ccache was trying to use it like it did. The simple solution was to run:
ccache-config --remove-links i686-pc-linux-gnu
After using this, things were compiling again using ccache. I do want to note that after sys-devel/gcc emerges during bootstrapping, you'll loose ccache because it will now use the new i686-pc-linux-gnu-gcc compiler instead of ccache. All I did to fix this was pause my bootstrap using Ctrl+Z, then type the command
ccache-config --install-links i686-pc-linux-gnu
and then typed in %1 to resume the boostrap job I just paused. I can't prove that this made it use ccache again, but it eased my mind.

So, to sum it up, if you want ccache when compiling from a stage one, you must use
ccache-config --remove-links i686-pc-linux-gnu
first, then
ccache-config --install-links i686-pc-linux-gnu
after sys-devel/gcc has emerged to make sure ccache works with your new compiler. Hope that helps someone out there!