I got this issue resolved just now. I had to use gcc to build the library
instead of ld. I found that if I used ld, I was having many issues, whereas
if I just used gcc to build the .so, all the issues went away. For example,
__umcpdi2 was a function that my code was getting linked with Glibc.
On Mon, 2008-10-13 at 22:11 -0400, Geoff Thorpe wrote:
What's the relation between this patch and the original poster's
question? I suspect that I haven't fully understood what your patch is
trying to resolve.
The question was 'how to load a DSO from within an engine'. That patch
just
How to load a DSO from within an engine?
I call DSO_load(NULL, mylibname, NULL, 0);
The code path I debugged is as follows:
#0 DSO_ctrl (dso=0x48ab98, cmd=2, larg=0, parg=0x0) at dso_lib.c:338
#1 0x2abb9c90 in DSO_load (dso=0x0, filename=0x2ae00888 mylibname,
meth=0x0, flags=0) at
Which version of openssl are you using?
Cheers,
Geoff
On Monday 13 October 2008 16:08:53 Pirasenna Velandai Thiyagarajan wrote:
How to load a DSO from within an engine?
I call DSO_load(NULL, mylibname, NULL, 0);
The code path I debugged is as follows:
#0 DSO_ctrl (dso=0x48ab98, cmd=2,
On Mon, 2008-10-13 at 13:08 -0700, Pirasenna Velandai Thiyagarajan
wrote:
How to load a DSO from within an engine?
See the code that this patch is mostly ripping out in favour of direct
linking:
http://git.infradead.org/users/dwmw2/openssl-tpm-engine.git?a=commitdiff;h=624a38a1
--
David
On Monday 13 October 2008 18:05:17 David Woodhouse wrote:
On Mon, 2008-10-13 at 13:08 -0700, Pirasenna Velandai Thiyagarajan
wrote:
How to load a DSO from within an engine?
See the code that this patch is mostly ripping out in favour of direct
linking:
