I am using visual studio 2008. I am compiling for 64 bit OS by doing perl Configure VC-WIN64A --prefix=D:\openssl_0.9.8k. The nmake /f ms\ntdll.mak install does copy the bin, lib, include and openssl.cnf files to the directory specified above. This procedure works for 0.9.8j and i have no problems getting it to work.
This error doesnt occur on the system where i build openssl. If i copy over the dll's to a different system along with the app that links to it, then i get these errors. -----Original Message----- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Dave Thompson Sent: 08 July 2009 06:35 To: openssl-users@openssl.org Subject: RE: cannot link to 0.9.8k dll's on windows > From: owner-openssl-us...@openssl.org On Behalf Of Vivek Subbarao > Sent: Monday, 06 July, 2009 06:34 > I have built openssl 0.9.8k library on windows 64 bit server 2003 OS. > I am linking my application to these dll's and lib's. But when i run my app > it displays the following errors and exits. > Auto configuration failed > 1396:error:02001015:system library:fopen:Is a directory:.\crypto\bio\bss_file.c: > 126:fopen('D:openssl_0.9.8k/ssl/openssl.cnf','rb') > 1396:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c > :131: > 1396:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\con > f\conf_def.c:199: Obviously it isn't able to open what you configured to be the default config file. Does that directory, and file, exist? TTBOMK the ms=Win build procedures don't do the install step, which 'make install' does on Unix/ish. I use my own (small) .bat file to copy the inc32 out32whatever and .cnf files, and ignore the man pages (I use a Unix copy for those). What compiler and especially C runtime library do you use? (Because that's what has to actually do the filename interp.) Does 64-bit still have the different library models like Win32 and need applink.c or something like it? For that matter are you compiling 64-bit, or just running on a 64-bit host? Possibly you need to use D:/openssl... (with the slash). You could try writing a small standalone test program that just opens a file, and verify what filenames work. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
