Re: Compile of Python 2.4.4 core dumps
Rob Gallagher wrote: On Wed, Feb 14, 2007 at 01:54:36PM +0100, Niclas Zeising wrote: Usually if a compile coredumps it's due to faulty memory or other hardware. Might be good to check that first. Especially since it worked flawlessly on another box. HTH //Niclas Thanks for the reply. I'm unsure if it's down to faulty memory because the machine is very new and I don't get core dumps when compiling or running any other software. Also, in my experience hardware faults have caused compiles to behave erraticlly, ie: bombing out at random stages in the build process - this core dump always occurs at exactly the same point (compilation of the curses module). I am experiencing the same problem (also running 6.2-RELEASE), so your hardware is not the cause. I'm afraid I don't have any helpful ideas, though. Bjørn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Compile of Python 2.4.4 core dumps
Hi, Upgrading to latest version of python24 port (2.4.4), the compilation process core dumps shortly after it begins. Here is the output leading up to the core dump: cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include -I/usr/ports/lang/python24/work/Python-2.4.4/Include -I/usr/ports/lang/python24/work/Python-2.4.4 -c /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o -L/usr/local/lib -lncurses -o build/lib.freebsd-6.2-RELEASE-i386-2.4/_curses.so Segmentation fault (core dumped) I'm running 6.2-RELEASE. I've upgraded another 6.2 box to python 2.4.4 without a problem, so I'm thinking the issue must lie with something on this system. rg -- We have an announcement to make... uh... on July 4th of this year, America will blow up the moon. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compile of Python 2.4.4 core dumps
On 2/14/07, Rob Gallagher [EMAIL PROTECTED] wrote: Hi, Upgrading to latest version of python24 port (2.4.4), the compilation process core dumps shortly after it begins. Here is the output leading up to the core dump: cc -DNDEBUG -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 -fPIC -fno-strict-aliasing -I. -I/usr/ports/lang/python24/work/Python-2.4.4/./Include -I/usr/local/include -I/usr/ports/lang/python24/work/Python-2.4.4/Include -I/usr/ports/lang/python24/work/Python-2.4.4 -c /usr/ports/lang/python24/work/Python-2.4.4/Modules/_cursesmodule.c -o build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o cc -shared -pthread -O2 -fno-strict-aliasing -pipe -D__wchar_t=wchar_t -DTHREAD_STACK_SIZE=0x2 build/temp.freebsd-6.2-RELEASE-i386-2.4/_cursesmodule.o -L/usr/local/lib -lncurses -o build/lib.freebsd-6.2-RELEASE-i386-2.4/_curses.so Segmentation fault (core dumped) I'm running 6.2-RELEASE. I've upgraded another 6.2 box to python 2.4.4 without a problem, so I'm thinking the issue must lie with something on this system. rg Usually if a compile coredumps it's due to faulty memory or other hardware. Might be good to check that first. Especially since it worked flawlessly on another box. HTH //Niclas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compile of Python 2.4.4 core dumps
Hi Niclas, On Wed, Feb 14, 2007 at 01:54:36PM +0100, Niclas Zeising wrote: Usually if a compile coredumps it's due to faulty memory or other hardware. Might be good to check that first. Especially since it worked flawlessly on another box. HTH //Niclas Thanks for the reply. I'm unsure if it's down to faulty memory because the machine is very new and I don't get core dumps when compiling or running any other software. Also, in my experience hardware faults have caused compiles to behave erraticlly, ie: bombing out at random stages in the build process - this core dump always occurs at exactly the same point (compilation of the curses module). ps: sorry about not wrapping my lines in the original post! ;-) rg -- We have an announcement to make... uh... on July 4th of this year, America will blow up the moon. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
