tronic wrote:
Noticed in your output:
Code:
cc1: /usr/local/include: Not a directory
That dir doesn't have to exist, but make sure there isn't a file called /usr/local/include. If there is, consider rm'ing it or mv'ing it out of the way.
Yep, you're right... "include" appears to be a text file in the /usr/local directory, the only text file in that exact path, by the way. Here's the first few lines of that file:
Code:
/* *************************************************************
RWhois Software
Copyright (c) 1994 Scott Williamson and Mark Kosters
Copyright (c) 1996-2000 Network Solutions, Inc.
See the file LICENSE for conditions of use and distribution.
**************************************************************** */
Looks like it had something to do with installing the rwhois client software I downloaded from rwhois.net the other day. It wasn't in Gentoo portage, so I had to download the source and compile it myself.
Moving it out of the way seemed to clear things up, though.
tronic wrote:
I'm running Gentoo on my Linode, tho with a 2.6 kernel. But same stuff and revs -- binutils, bzip2, gcc, etc.
What version of binutils are you running? I think a nasty bug slipped in at -r3 that caused some weirdness in building stuff. It's fine at -r1 and fixed in -r4.
I'm guessing you're at -r1 for binutils; if so, that's good.
Looks like that wasn't the case.
Code:
* sys-devel/binutils
Latest version available: 2.15.92.0.2-r1
Latest version installed: 2.15.92.0.2-r1
tronic wrote:
Finally, I saw on a friend's Gentoo box yesterday where builds would fail because his system's battery was dead so on boot, the clock reverted to 2001. Result was, being off by 4 years threw stuff depending on timestamp checks to point of breaking. After the clock was corrected with NTP, builds worked ok.
So check 'date' to make sure the date and time is 'close enough' (within a few minutes of the actual time). I can't imagine this being an actual issue with Linodes, but doesn't hurt to double check.
The system date is more or less close to my own system clock at home, the latter being automatically synced with a time server every hour.
Conclusion:
I moved the file located at /usr/local/include out of the way, re-ran emerge with the same parameter, and now it's finally installing without the annoying halting error. Yay!
Thanks for all the help, guys! Looks like I have to stick around in the "beginner" end of the Linux pool for a little while longer...
FAQ
Search
Members
Register
Login [ Anonymous ]
