[erlang-questions] Erlang crypto_drv in R13B02/03 fails to load on amd64-Solaris2.10
Mon Nov 23 12:19:39 CET 2009
No, I don't think that the issue is to do with paths. The loader
_does_ find the crypto_drv.so file, and fails to load it because
"symbol (unknown): value 0xfffffd7ffd514fdf does not fit." I began to
think that it was an AMD ABI "memory model" issue, where a 64 bit
offset could not fit into a 32 bit value of an address register
relative memory access instruction.
Per pointed out that there are symbols in the crypto_drv.so file which
suggest that the linker is being invoked with the wrong options,
resulting in what smells like a stand-alone executable file with a
main() function, not a shared library object.
I'm going to continue hacking the Makefiles to see if adding the
suggested -shared option to the crypto_drv linker command makes a
On Mon, Nov 23, 2009 at 5:10 AM, Scott Lystig Fritchie
> Hi, Per and Chandur and Peter-Henry ... I don't believe we've suffered
> from this exact problem, but perhaps it's related? At Gemini we build
> the VM with "./configure --prefix=/some/weird/place" and then really
> install the whole package to /some/other/dir/entirely.
> IIRC, we've had to add an "env
> LD_LIBRARY_PATH=/some/other/dir/entirely/...openssl/lib" wrapper in our
> /etc/init.d/appthingie script's invocation of our daemons.
More information about the erlang-questions