OK, I emerge-d gnome, it installed OK, but when I wanted to start gnome-session I was getting a lot of errors. After a lot of strace-ing... actually, it is easier to explain what the problem is by showing the workaround: cd /var/tmp/portage && mkdir foo && ln -s / foo/image for i in bonobo-activation-1.0.3 gnome-panel-2.0.9 gnome-session-2.0.7 gnome-vfs-2.0.4-r2 nautilus-2.0.7; do ln -s foo $i done My gnome starts ok now. However, the mentioned packages were still, looking for their stuff in ${D}, so this is only a temporary workaround for me. Some non-traditional things I did were, that I was using emerge -b, and secondly - I didn't emerge -b gnome, but rather checked what that would do, and installed most of the stuff manually, since I didn't want to install some of the things from the bundle (gnome-terminal for example).
oh, yes... in the end I DID emerge -b gnome after all :)
How did you 'install stuff manually' exactly ? It looks as if the ebuilds never got trough their emerge step (where the builded package gets merged into the live filesystem).
I was only doing "emerge -b packagename" until I got tired and "emerge -b gnome"-ed in the end. My computer did an "emerge -b --emptytree gnome" overnight... and it works now... Weird!
Not really, apparently you only made packages and didn't merge the files into the system. -b should do it, but for some reason it didnt (?). anyway, closing.
If I only made the packages, how did gnome-session end up in my path? And what about the other stuff that gnome-session was executing - nautilus, gnome-settings-daemon and similar. After all, the problems started after I did a rm -rf /var/tmp/portage/* (and then I had to do the workaround with the symlinks), but I now realize that I had forgotten to mention that. It seems that the files were installed where they were supposed to be installed, but the internal paths (maybe hard-coded at compilation or installation) were pointing to the ${D} directory. I am just speculating on the subject... I am not complaining now, just want to have this reported...
Well, if it's a reproducable problem and you can give a bit clearer report i would like to have it, but with the way it looks now i can't make much of it. Can be a libtool issue, can be a portage problem..
