Summary: | ORBit2-2.12.3 fails to emerge: `TTypeCode' undeclared identifier | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | veacheslav <veacheslav> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | admorgan, emergetw, gentoo-bugs, zambizzi |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
veacheslav
2005-10-18 01:30:41 UTC
try re-emerging libIDL and report back, Thanks! (In reply to comment #1) > try re-emerging libIDL and report back, Thanks! Thanks for help! It didn't help. Also I searched "TTypeCode" identifier in all *.h files of /usr/include and didn't find nothing. I was having the identical problem on a dual core athlon64, with -j3 MAKEOPTS. Rebuilding libIDL and then orbit did not resolve the problem. Setting -j1 and retrying the orbit emerge did not help either, but rebuilding libIDL with -j1 first, and /then/ rebuilding orbit, did. Buggy makefile in libIDL perhaps? I also have a dual core athlon64 but what you describe doesn't work for me. I tried everything in here and most everything in this thread http://forums.gentoo.org/viewtopic.php?t=157488 . Finally I tried setting the date far in the future as suggested in that thread. It worked. Could someone please explain to me why this worked? Now it works (after emerge --sync). (In reply to comment #5) > I tried everything in here and most everything in this thread > http://forums.gentoo.org/viewtopic.php?t=157488 . Finally I tried setting the > date far in the future as suggested in that thread. It worked. Could someone > please explain to me why this worked? I was having the same error with Orbit-2.12.4 Tried changing my CFLAGS and MAKEOPTS etc, Setting my clock 2 months into the future worked for me as well Ran into this same problem with Orbit2. I discovered that MANY of my files are dated in the future. I was in the middle of an emerge -e world and it seems that abut half of the files that were installed were done so with a future date. The problem is so wide spread that I will have to set my clock forward or "touch" the entire file system which we all know is a Bad Thing(tm). This is not a problem with my hardware (I use NTPD and the clock is and was correct), this is a deeper problem. Portage is installing things with an incorrect timestamp and there are several threads in the forums about it already so I *know* it isn't just me having a buggy clock. I'm opening a seperate bug about this since Orbit has nothing to do with the problem. this bug has to do with file dates set to times in the future, something which we cannot fix. *** Bug 140544 has been marked as a duplicate of this bug. *** *** Bug 150056 has been marked as a duplicate of this bug. *** For people who couldn't solve the problem using information from this bug, here's what to do: emerge -1 glib popt && emerge -1 libIDL orbit *This* should work - for me it sure did :-) |