On Thu, 30 Nov 2006, Brad Cavanagh wrote:
> On Thu, 30 Nov 2006, Peter W. Draper wrote:
>
>> gcc -o javatest javatest.c /star/starjava/i386/libsplat.jnilib \
>> /star/starjava/lib/i386/libjniast.jnilib
>>
>> The equivalent worked for me under ppc.
>
> Okay, this helped. Doing this lead to:
>
> gala:~/temp bradc$ ./javatest
> dyld: Library not loaded: /usr/local/lib/libgcc_s.1.0.dylib
> Referenced from:
> /Users/bradc/development/starlink/java/source/splat/build/lib/i386/libsplat.jnilib
> Reason: image not found
> Trace/BPT trap
>
> This is absolutely right, there's no /usr/local/lib/libgcc_s.1.0.dylib, it's
> actually buried in my /star tree. I should have noticed this earlier, as
> 'otool -L libsplat.jnilib' showed that same file. Anyhow, using
> install_name_tool I changed where libsplat.jnilib looks for
> libgcc_s.1.0.dylib, recompiled, and reran javatest. This segfaulted, so
> running it in gdb gave:
>
> (gdb) run
> Starting program: /Users/bradc/temp/javatest
> Reading symbols for shared libraries .+..+ done
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0x4e49474f
> 0x4e49474f in ?? ()
> (gdb) bt
> # 0 0x4e49474f in ?? ()
> # 1 0x01682a12 in Java_uk_ac_starlink_splat_imagedata_NDFJ_nOpen
> (env=0x357d0, class=0xd24a838b, string=0x38800004) at NDFJImpl.c:147
> Previous frame inner to this frame (corrupt stack?)
> (gdb)
>
>
> Hope this helps. :-)
Actually it probably does. I didn't intend the test program to run
successfully (just test what symbols or libraries turn up missing, as it
did), so it's dying just where it should, that's when it accesses the NDF
name. Maybe this library will now load into a JVM?
I guess if it's still broken it there could be some incompatibilities with
this libgcc_s and the system one (should be in /usr/lib), in which case
you'll need to persuade g95 to use the system versions. We'd had some
success with just replacing such libraries in g95 with links to the system
ones (needed for FC/6, which uses gcc4.1).
> If it doesn't, next week I can leave my laptop at work overnight if you want
> to login and muck around with things yourself. I'm not going to tonight
> because I'm taking Friday off and would really like my laptop for the
> weekend. :-)
OK, we'll see how things go.
Cheers,
Peter.
|