Hi,

You are using the wrong build environment. Be sure to launch the right
command prompt using the link installed under program files by Visual
studio 2008 under the name "Visual Studio 2008 x64 Win64 Command
Prompt". You can also use the batch file named "vcvarsamd64.bat" to set
the right build environment: this file resides under
"VCInstallDir\VC\bin\amd64".

Cheers,
--
Mounir IDRASSI
IDRIX
http://www.idrix.fr

Bernhard Marschall wrote:
> Hi,
>
> Sorry to ask again, but I only found the question in the mailing list
> archive but no answer.
>
> I tried to build OpenSSL 0.9.8k on 64-bit Windows, but it failed.
>
> As mentioned in the docu I called
>
>  > perl Configure VC-WIN64A
>  > ms\do_win64a
>  > nmake -f ms\ntdll.mak
>
> link /nologo /subsystem:console /opt:ref /dll /out:out32dll\libeay32.dll 
> /def:ms/LIBEAY32.def @C:\Users\build\AppData\Local\Temp\2\nmEB5C.tmp 
> tmp32dll\uplink.obj : fatal error LNK1112: module machine type 'X86' 
> conflicts with target machine type 'x64'
> NMAKE : fatal error U1077: 'C:\win32app\devstudio_2008\VC\BIN\link.EXE' : 
> return code '0x458'
> Stop.
>
> Any ideas how to fix this?
>
> Best regards,
> Bernhard
> --
> ------------------------------------------------------------------------
> Bernhard Marschall, Software Development
> Hyperwave AG, Albrechtgasse 9, A-8010 Graz
> Tel +43 (0) 316 820918 32, Fax +43 (0) 316 820918 99
> Landesgericht Graz, FN 269228z, Vorstand: Herwig Gangl, Gerhard Pail
> ------------------------------------------------------------------------
> ______________________________________________________________________
> OpenSSL Project                                 http://www.openssl.org
> Development Mailing List                       [email protected]
> Automated List Manager                           [email protected]
>   
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to