but I have found
no explanation or resolution.
https://marc.info/?l=openssl-users=141216400714219=2
Can someone provide guidance for resolving this error?
Craig Weeks | Senior Software Engineer, Support Response Team (SRT)
craig_we...@trendmicro.com<mailto:richard_fang...@trendmicro.com>
142
for resolving this error?
Craig Weeks | Senior Software Engineer, Support Response Team (SRT)
craig_we...@trendmicro.com<mailto:richard_fang...@trendmicro.com>
14231 Tandem Blvd, Austin TX 78728
www.trendmicro.com<http://www.trendmicro.com>
TREND MICRO EMAIL NOTICE
The informati
I think you are right about some kind of munging of the .c source via some
header file. I just don't know exactly how to track that down. Here are the
files that reference _Stoul in libcrypto.a:
ec_pmeth.c
rsa_pmeth.c
dsa_pmeth.c
dh_pmeth.c
b_sock.c
asn1_gen.c
a_strnid.c
ocsp_ht.c
ts_conf.c
)
craig_we...@trendmicro.com
14231 Tandem Blvd, Austin TX 78728
www.trendmicro.com
TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential
and may be subject to copyright or other intellectual property protection.
If you are not the intended recipient
Ok, I see *how* this is happening, but I don't understand why. In the version
of stdlib.h that I am including I see:
*-*-*-*-*-*-*-*-*-*
#if defined(__cplusplus) && !defined(_NO_CPP_INLINES)
[snip]
#else /* defined(__cplusplus) && !defined(_NO_CPP_INLINES) */
_C_LIB_DECL
/*
or disabled.
Craig Weeks | Senior Software Engineer, Support Response Team (SRT)
craig_we...@trendmicro.com<mailto:richard_fang...@trendmicro.com>
14231 Tandem Blvd, Austin TX 78728
www.trendmicro.com<http://www.trendmicro.com>
TREND MICRO EMAIL NOTICE
The information contained i
I’m interested in the rest of this story. Does compiling a separate library
for linking work for you now? Our product runs on two platforms: one
Pentium-based and one Mips-based. The Pentium build works fine but the Mips
build fails at link time with unresolved function references.
From:
We have recently upgraded our product to 1.0.2k. We are getting this error on
a packet sent to us from our browser-based user interface. I really need some
suggestions as to how to debug this problem. I know it is in our code rather
than OpenSSL but I have no idea how to dig into what is
