This also happens when compiling 'wget' but there I choosed to 'emerge --resume --skip-first'. But now I want to get to the bottom with this 'clock_gettime'-errors. I have FEATURES="-confcache" in my /etc/make.conf.

Another solution would be to remove gstreamer but as it keeps ketting installed I guess some other package is depending on it... How do I check that?

Thanks in advance!_________________QX9650, P5E64WS Pro, 4x1GB

Last edited by blossa on Sun Feb 24, 2008 11:21 pm; edited 1 time in total

OK, I don't know if this'll work. I'm going to guess "No, it won't", but what the hell. So, attempt this:

Code:

cp /var/cache/edb/mtimedb /root/ && emerge -1 glibc

If that's successful, then do:

Code:

cp -f /root/mtimedb /var/cache/edb/ && emerge --resume

Basically, you're saving the current state of the "emerge -e world", then restoring it after the other emerge completes. Even if this doesn't fix the problem, it's a useful trick._________________Thomas S. Howard

You are absolutly right, 'what the hell' is a very good reason to try it. I will try it shortly and I will let you know how (and if) it works. Thank you!

About the trick you mention.... I guess one can use it for other cases. Like when emerging world and portage complains about 're-emerge that-package with USE="that-option" '. Until now I have done Like i was told and then started all over with emerging world._________________QX9650, P5E64WS Pro, 4x1GB

It stopped now at alsa-lib. But doing your trick once again also solved the alsa-lib problem. But I cannot understand why I have to do this everytime I get to a package that gives me the 'clock_gettime' error. Anyone who can explain that?_________________QX9650, P5E64WS Pro, 4x1GB