On Tuesday 05 December 2006 01:16, Rachel Florentine wrote: > 858376 > > ----- Original Message ---- > From: Kris Kennaway <[EMAIL PROTECTED]> > To: Rachel Florentine <[EMAIL PROTECTED]> > > >Uh, what I said. "Fresh binary media" = either reinstall from an > > iso image, or extract a copy of the damaged files from the > > freebsd release media in another way (e.g. fetch the base.* files > > from the ftp site, and pass through cat | tar -xfj -). > > Okay, please walk me through this one, since I can't afford to > screw it up. The server is on the other side of the planet, so > reinstalling from an iso is impractical. How do I fetch the base > files? TIA, > Rachel > >
You're barking up the wrong tree. There's nothing at all wrong with your system compiler. See your other thread about your problems with Zope. You've mistaken using python to repair the python libraries that interface with the C libraries with using gcc to fix something. You admit that you were able to successfully compile and install Zope from the ports system, which uses the system C compiler. If you don't believe me try installing some other ports, or even cd /usr/src && make buildworld. (which won't actually touch anything, it's completely safe to do) If you run into compiler issues doing that *THEN* you can start to deal with a corrupted C compiler. Until then I think you'd be money ahead to look at the FreeBSD-specific patches that are applied during the Zope build from the port, and the additional magic that is done in the port's Makefile. I suspect the differences between the port and your hand installation are the root of your problem. -- Thanks, Josh Paetzel _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
