Timothy,
On Fri, Aug 1, 2008 at 2:30 PM, Timothy Wall <twal...@dev.java.net> wrote:
On Aug 1, 2008, at 4:18 PM, Corey Puffalt wrote:
From Googling around it seems to be the shared library that corresponds to
the static library (libgcc.a) which I do have on my system. Not sure if
there's a way for me to force the libffi.so to be statically linked to
libgcc.a instead of dynamically linking to libgcc_s.so? Anyways, it looks
like I'm going to have to pester the administrators to re-install the gnu
toolchain and hope that resolves the issue...
Well, we need the static libffi, not the shared one. Maybe there's a flag
to the libffi config like --disable-dynamic? You might also be able to
force static linkage of gcc with -static-libgcc passed to the linker.
It looks like there might be a flag --disable-shared. After poking around a
bit I found a FFI_CONFIG= variable in the Makefile in jnalib/native (I tried
running the libffi configure directly but the JNA Makefile forbids that.
Interestingly the FFI_CONFIG= variable contained a --disable-static
directive?? Anyways, things are still blowing up. I seem to be in over my
head in terms of getting this to work and may have abandon JNA completely
unless someone else is able to produce a working build.
How would I go about passing -static-libgcc to the linker?
Thanks for your interest.
Corey
22 messages in net.java.dev.jna.usersRe: [jna-users] JNA & Solaris 8
.log
