In order to install GTK applications, remember to set your PKG_CONFIG_PATH to /usr/local/lib/pkgconfig, download the application of your choice, run ./configure, make and make install. For me, it worked with gqview. In future, I wanna try to compile rox and scite.

No, I haven't sorry. I don't really have an interest in those programs. But I successfully compiled gqview, scite and rox. Check what happens, if you do ACCEPT_KEYWORDS="ppc" emerge -p gaim . If gtk+ is the last dependency before gaim, it should be possible to compile gaim, too.
Right now, I don't have my iBook with me. But if you like, I can try to compile these programs within in the next few days and post my results here.

It's probably possible. But to tell you the truth, I don't know how. I am not a Gentoo developer. At the moment, I'm rather busy with final exams. Once I have some more time, I will study ebuilds and stuff. it wouldn't be a bad thing, if somebody could repair the pango ebuild first. If that is done, it shouldn't be a problem to make ebuild for gtk, gqview and gaim. Does anybody know, who is in charge of Portage for MacOSX development?

I've tried to repair the pango ebuild. But unfortunately, I didn't succeed. I always get a libtool error even when I exclude the gentoo libtool patches from the ebuild. Has anybody managed to emerge pango successfully? Without pango, it won't be possible to install gtk+.

That's great news! Have you performed any rituals to make it work or have you simply emerged it? I haven't tried emerging pango for quite some time now. But now I'm very anxious to do so. Now, I'm running Tiger on my machine, maybe that makes things easier....

the most contentious is the one for XML Parser perl module. I used the perl module eclass which the perl herd people disapprove of. (it works great though).

another key is to add both 'macos' and 'ppc-macos' to your USE flags.

also, I've needed to use gcc 3.3. you can use the 'gcc_select' program in tiger to switch your system to use gcc 3.3.

and finally, pango emerged, but the shared libraries didn't have the .dylib filemame extension, so the configure script for gtk+ couldn't find them. some symbolic links fixed that.

now if only I could get gtk+ to build... anyway I've posted the last error I'm getting, and I also filed a bug for it. when I started out it looked hopeless, now it's almost there!_________________http://www.desertsol.com/~kevin/ppc

here's a list of all the packages I currently have emerged on my system.

I almost forgot; I had to emerge automake 1.7.9-r1 since gtk+ uses features from that version. I also had to export some environment variables so it would use the newer automake. I still need to file a bug for automake.

Looks like you did a great jobbing making Darwin-portage emerge automake.
How did you do that? Although all automake ebuilds have the "~ppc-macos" flag, portage refuses to emerge it.
Now, this is what I did so far:
Using gcc-4.0 (!), I emerged

I think it worked!
I emerged automake as your wrote me and added symbolic links for pango-dylibs.
Unfortunately, setting environment variables for automake-1.7.9 didn't work for me, so I created a symbolic link from automake to automake-1.7. Then, I emerged gtk+ by path like

Code:

emerge /usr/portage/x11-libs/gtk+/gtk+-2.4.14.ebuild

And now, it seems to have been successfully emerged. I haven't to emerge any gtk-depending applications yet. But, I'm going to try with scite soon. As it appears, I will have to make symbolic links for the gtk+-dylibs, too! But that shouldn't be a problem...
Wish me luck! And thanks for your input![/code]

That's really odd... Maybe it's because I didn't set the jpeg flag, I don't know.
The really odd thing is that I successfully manage to emerge gtk+, but gtk+-based applications just like scite or gqview don't recognize it!
As for now, I have stopped dealing with gtk+ under OSX. At the moment I have to worry about things that are far more important than that. But please keep me posted. This is a most fascinating thread!

just to let all three people who care know, i got it working! the only differences between my approach and others is the following:

--emerged automake with all dependencies using emerge /usr/portage/sys-devel/automake-whatever/blah.ebuild approach unless there is a cyclical dependency, then i emerged the wrapper first using the ebuild blah.ebuild fetch unpack compile install qmerge approach.
--i emerged EVERYTHING including gtk+ 2.4 (which i had to download the ebuild/digest/patches for since 2.4 has been removed from portage).
--i wasn't afraid to use FEATURES="-collision-protect", although i feel lucky it didn't fubar anything in the mac os base.

but i haven't tested if gtk really works or not. 2.4 is a really old, deprecated version of gtk. my goal is to get 2.6 working right now so i can run most applications out there. i'll deal with 2.8 when i have time. so far, i'm stuck at the new pango emerge. i'll post my results for people later on if anyone's interested.