From octave-maintainers-request at bevo dot che dot wisc dot edu Fri Mar 26 01:01:08 1999 Subject: `make' fails on SunOS 5.5 From: "John W. Eaton" To: NAKAJI Hiroyuki Cc: octave-maintainers at bevo dot che dot wisc dot edu, nakaji@zeisei6.dpri.kyoto-u.ac.jp Date: Fri, 26 Mar 1999 01:00:58 -0600 (CST) On 24-Mar-1999, NAKAJI Hiroyuki wrote: | Bug report for Octave 2.0.13.96 configured for sparc-sun-solaris2.5 | | Description: | ----------- | | With egcs-1.1.1 and f77-4.0(SPARCCompiler), link stage fails. Error | message is | | c++: unrecognized option `-rdynamic' | Undefined first referenced | symbol in file | set_new_handler ../src/liboctinterp.a(sighandlers.o) | ld: fatal: Symbol referencing errors. No output written to octave | collect2: ld returned 1 exit status | gmake[2]: *** [octave] Error 1 | gmake[2]: Leaving directory `/net/zeisei8/export/local/src/octave-2.0.13.96/src' | gmake[1]: *** [src] Error 2 | gmake[1]: Leaving directory `/net/zeisei8/export/local/src/octave-2.0.13.96' | gmake: *** [all] Error 2 A quick workaround for this problem would be to change RDYNAMIC_FLAG = -rdynamic to RDYNAMIC_FLAG = in Makeconf. But the real fix involves figuring out why Octave's configure script thinks that linking with -rdynamic will succeed. Can you tell me what happens if you compile (and link) a simple program with g++ -rdyanmic foo.cc on your system? For example, a hello world program like #include int main (void) { cout << "hello world\n"; } Does it fail? What is the exit status of g++? Thanks, jwe