> From: owner-openssl-us...@openssl.org On Behalf Of Jeffrey Walton > Sent: Wednesday, 06 February, 2013 16:59 > To: openssl-users@openssl.org > Subject: Re: fipslink > > On Wed, Feb 6, 2013 at 2:40 PM, Memmott, Lester > <lester.memm...@landesk.com> wrote: > > Jon, > > > > I'm having trouble with fipslink as well and thought it > might help to compare notes. These are the linker errors I'm > getting using Visual Studio 2008: > > fips_premain.obj : error LNK2001: unresolved external > symbol "unsigned char * FIPS_signature" (?FIPS_signature@@3PAEA) > > fips_premain.obj : error LNK2001: unresolved external > symbol "void const * __cdecl FIPS_text_start(void)" > (?FIPS_text_start@@YAPBXXZ) > > fips_premain.obj : error LNK2001: unresolved external > symbol "unsigned int __cdecl FIPS_incore_fingerprint(unsigned > char *,unsigned int)" (?FIPS_incore_fingerprint@@YAIPAEI@Z) > > > > What linker errors do you get? > It looks like you are not compiling fips_premain.c (that's where those > symbols are allocated storage). > I don't think so. In my copy they are *referenced* in fips_premain.c, and allocated/defined in fips.c and fips_canister.c .
Those error messages look like fips_premain.c was compiled as C++ instead of C. Since by design C++ is a superset of "good" C this doesn't cause errors. If OP is compiling in VisualStudio/VisualC++ (not just linking) in my experience VisualStudio defaults to "force C++" and you have to manually reconfigure to allow C. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
