no stacktrace available
Tue Dec 14 07:09:00 GMT 2004
% gcj -v
Reading specs from /usr/pkg/gcc3/lib/gcc-lib/i386--netbsdelf2.0/3.3.4/specs
Reading specs from
rename spec lib to liborig
Configured with: ./configure --prefix=/usr/pkg/gcc3
--host=i386--netbsdelf2.0 --enable-shared --enable-languages=java
Thread model: posix
gcc version 3.3.4
regarding building a new one, i'm not sure how magic the pkgsrc
scripting is. i'll see what i can find out.
if i can use the existing toolchain and just rebuild gcc's c/c++/java,
it will be a lot more possible.
Michael Koch wrote:
>Am Dienstag, 14. Dezember 2004 07:33 schrieb Bart Locanthi:
>>hmm, on linux it does just work. nothing to issue a stack trace
>>-g on netbsd doesn't help.
>>no idea how gcj was built - i installed a standard package. also no
>>idea what other binary magic netbsd uses.
>>back in the netbsd 1.6 days there was a thread/gc interaction that
>>kept me away. lots of thread improvements in 2.0; i'll try out a
>>simpler example to satisfy myself that that problem at least has
>gcj -v will tell you the configure flags. Can you try the latest
>stable release of gcj: 3.4.2 ? Or gcc cvs HEAD ?
More information about the Java