I'm using a Nextstep system. I run the configure script but it claims that my compiler is a cross-compiler (produces the message: 'checking whether cross-compiling... yes') and produces nonsense results.
Your compiler seems to be producing code which cannot always be executed. There seems to be a problem with the C++ name demangler causing the linker to occasionally generate bad code. This problem occurs most frequently when the using NFS file-systems. A workaround (at least for Nextstep 3.3 Developer) is to modify the shell script "/bin/ld++" and remove the pipe to the "c++filt" program. "/bin/ld++" then just contains a call to the linker (i.e. "ld $*").
I'm using a Nextstep system. I run the configure script but it claims that my compiler is a cross-compiler (produces the message: 'checking whether cross-compiling... yes') and produces nonsense results.
Your compiler seems to be producing code which cannot always be executed. There seems to be a problem with the C++ name demangler causing the linker to occasionally generate bad code. This problem occurs most frequently when the using NFS file-systems. A workaround (at least for Nextstep 3.3 Developer) is to modify the shell script "/bin/ld++" and remove the pipe to the "c++filt" program. "/bin/ld++" then just contains a call to the linker (i.e. "ld $*").