Re: Corrupted C Compiler
On Mon, 4 Dec 2006, Rachel Florentine wrote: From: Jan Grant [EMAIL PROTECTED] I don't think it makes much sense, no. Zope is python-based and unless you're building products that rely on native libraries, what you describe doesn't sound like an accurate diagnosis. It's more likely (this is a stab in the dark) that you're running a script to regerate .pyc files; these are precompiled python bytecode files that are built from the corresponding .py files. I don't have my references in front of me, but I ran into an error when I tried to runzope that I didn't understand, so I yahoo'd it and discovered that my c libraries were corrupted. It was recommended I run a certain command to clean them up. I ran that command and everything went smoothly. I repeated this process a few times. So yes, I'm sure that's what I did. When you have a chance, it'd be nice to get a detailed error report (including the command you were running to clean up the libraries). -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ ...and then three milkmaids turned up (to the delight and delactation of the crowd). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted C Compiler
81- Original Message From: Jan Grant [EMAIL PROTECTED] When you have a chance, it'd be nice to get a detailed error report (including the command you were running to clean up the libraries). I get this error when I try to runzope: ImportError: No module named cPersistence I yahoo'd this page: http://aspn.activestate.com/ASPN/Mail/Message/zope-List/1985451 which told me about the problem with my corrupted files (c extensions) and said I needed to recompile them with this command: python setup.py build_ext -if which takes care of that problem. What is interesting is that I do not have this problem if I compile from port! Now, all I'm doing is the configure-make-make install-make instance dance, which is a no-brainer. TIA, Rachel __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted C Compiler
On Tuesday 05 December 2006 05:38, Rachel Florentine wrote: 81- Original Message From: Jan Grant [EMAIL PROTECTED] When you have a chance, it'd be nice to get a detailed error report (including the command you were running to clean up the libraries). I get this error when I try to runzope: ImportError: No module named cPersistence I yahoo'd this page: http://aspn.activestate.com/ASPN/Mail/Message/zope-List/1985451 which told me about the problem with my corrupted files (c extensions) and said I needed to recompile them with this command: python setup.py build_ext -if which takes care of that problem. What is interesting is that I do not have this problem if I compile from port! Now, all I'm doing is the configure-make-make install-make instance dance, which is a no-brainer. TIA, Rachel That rebuilds the python C library interface stuff I believe, but doesn't have anything at all to do with the system C compiler. There is nothing wrong with your system C compiler. If you look at the Zope port there are a bunch of FreeBSD-specific patches and some additional magic is performed after the build that would also be FreeBSD-centric. I suspect your problems perhaps stem from the fact that installing Zope by hand doesn't give you these patches. -- 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]
Re: Corrupted C Compiler
- Original Message From: Josh Paetzel [EMAIL PROTECTED] That rebuilds the python C library interface stuff I believe, but doesn't have anything at all to do with the system C compiler. There is nothing wrong with your system C compiler. Well, that's a relief! Thanks! If you look at the Zope port there are a bunch of FreeBSD-specific patches and some additional magic is performed after the build that would also be FreeBSD-centric. I suspect your problems perhaps stem from the fact that installing Zope by hand doesn't give you these patches. Okay. That makes sense :) Thanks again :) Rachel Any questions? Get answers on any topic at www.Answers.yahoo.com. Try it now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Corrupted C Compiler
106Hi; I entered the following stupid command: cp -R /* /ad2 thinking that would copy the contents of my working HD to my new 1/2 teraflop HD (ad2). What it did was manage to wipe out some very important files (thank goodness I had up-to-date backups) and it appears to have corrupted gcc...my C compiler. I deduce this because when I go to build Zope (as an example) from source I have to run a script afterwards that repairs the broken C files. (This, strangely, is not the case if I build Zope from port.) So, my questions for you programmers more experienced than I, are: 1) Does my assessment make sense? Is gcc corrupt? 2) Whether it is or not, how should I troubleshoot/fix my problem? It seems to me I should re-install FBSD, but how? TIA, Rachel Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted C Compiler
On Monday 04 December 2006 07:05, Rachel Florentine wrote: 106Hi; I entered the following stupid command: cp -R /* /ad2 thinking that would copy the contents of my working HD to my new 1/2 teraflop HD (ad2). What it did was manage to wipe out some very important files (thank goodness I had up-to-date backups) and it appears to have corrupted gcc...my C compiler. I deduce this because when I go to build Zope (as an example) from source I have to run a script afterwards that repairs the broken C files. (This, strangely, is not the case if I build Zope from port.) So, my questions for you programmers more experienced than I, are: 1) Does my assessment make sense? Is gcc corrupt? 2) Whether it is or not, how should I troubleshoot/fix my problem? It seems to me I should re-install FBSD, but how? TIA, Rachel It's not immediately clear to me what you mean by repairing broken C files. The port uses the Zope source and the system compiler, presumably the same source and compiler you are using to build it by hand. Are you sure you aren't just 'doing it wrong' ? If you really suspect gcc is corrupted then some sort of binary repair is really your only option. A make buildworld/make installworld is unlikely to be feasible. -- 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]
Re: Corrupted C Compiler
On Mon, 4 Dec 2006, Rachel Florentine wrote: I entered the following stupid command: cp -R /* /ad2 thinking that would copy the contents of my working HD to my new 1/2 teraflop HD (ad2). What it did was manage to wipe out some very important files (thank goodness I had up-to-date backups) and it appears to have corrupted gcc...my C compiler. I deduce this because when I go to build Zope (as an example) from source I have to run a script afterwards that repairs the broken C files. (This, strangely, is not the case if I build Zope from port.) So, my questions for you programmers more experienced than I, are: 1) Does my assessment make sense? Is gcc corrupt? No, or the port would not be able to build correctly. That is the main point of the ports system, of course: to correctly build software on FreeBSD. 2) Whether it is or not, how should I troubleshoot/fix my problem? It seems to me I should re-install FBSD, but how? An additional feature of the ports system is that it makes deinstalling ported software easy. Since you've installed software without using the port, making sure all of the files and side-effects are removed when deinstalling is much more difficult. My suggestion would be to reinstall FreeBSD from scratch. Do a clean install of FreeBSD, then back it up with dump as shown in the Handbook. In fact, any time a question comes up, check the Handbook first for the preferred way to solve it. Add applications from ports so they'll be installed correctly for FreeBSD and will be easy to update. Make backups with dump as you go, so you can restore to a known-good setup. Once you get a Zope instance installed, make an additional backup of it by copying the Data.fs file somewhere safe. With all that done, you can start experimenting. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted C Compiler
- Original Message From: Josh Paetzel [EMAIL PROTECTED] It's not immediately clear to me what you mean by repairing broken C files. The port uses the Zope source and the system compiler, presumably the same source and compiler you are using to build it by hand. Are you sure you aren't just 'doing it wrong' ? Positive. If you really suspect gcc is corrupted then some sort of binary repair is really your only option. A make buildworld/make installworld is unlikely to be feasible. So how do I do that? Rachel Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted C Compiler
On Mon, 4 Dec 2006, Rachel Florentine wrote: Hi; I entered the following stupid command: cp -R /* /ad2 thinking that would copy the contents of my working HD to my new 1/2 teraflop HD (ad2). What it did was manage to wipe out some very important files (thank goodness I had up-to-date backups) and it appears to have corrupted gcc...my C compiler. I deduce this because when I go to build Zope (as an example) from source I have to run a script afterwards that repairs the broken C files. (This, strangely, is not the case if I build Zope from port.) So, my questions for you programmers more experienced than I, are: 1) Does my assessment make sense? Is gcc corrupt? I don't think it makes much sense, no. Zope is python-based and unless you're building products that rely on native libraries, what you describe doesn't sound like an accurate diagnosis. It's more likely (this is a stab in the dark) that you're running a script to regerate .pyc files; these are precompiled python bytecode files that are built from the corresponding .py files. That's a part and parcel of readying Zope for production - however, Zope will run without those .pyc files (the .py files are compiled on first load instead). I suspect that that's what's going on. Cheers, jan -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Usenet: The separation of content AND presentation - simultaneously. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted C Compiler
76 - Original Message From: Jan Grant [EMAIL PROTECTED] I don't think it makes much sense, no. Zope is python-based and unless you're building products that rely on native libraries, what you describe doesn't sound like an accurate diagnosis. It's more likely (this is a stab in the dark) that you're running a script to regerate .pyc files; these are precompiled python bytecode files that are built from the corresponding .py files. I don't have my references in front of me, but I ran into an error when I tried to runzope that I didn't understand, so I yahoo'd it and discovered that my c libraries were corrupted. It was recommended I run a certain command to clean them up. I ran that command and everything went smoothly. I repeated this process a few times. So yes, I'm sure that's what I did. Rachel Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
