So how to build on AMD 64 and Intel EM64T I summarize here:
1. perl Configure VC-WIN32
2. ms\do_ms
3. perl ms/uplink.pl win64a uptable.asm
4. ml64 -c uptable.asm
5. modify the mak files as above
6. nmake -f ms\ntdll.mak
I hope it helps others out.
As per today the above unsupported
Andy Polyakov writes:
As per today the above unsupported instructions have to be declared
officially invalid. This is because if built according to above, the
resulting .dll will be binary incompatible with one built according to
newly introduced supported procedure:
- perl Configure
As per today the above unsupported instructions have to be declared
officially invalid. This is because if built according to above, the
resulting .dll will be binary incompatible with one built according to
newly introduced supported procedure:
- perl Configure VC-WIN64A [or VC-WIN64I for
Hi,
newly introduced supported procedure:
- perl Configure VC-WIN64A [or VC-WIN64I for Itanium];
- ms\do_win64a [or ms\do_win64i for Itanium];
- nmake -f ms/ntdll.mak;
This applies to upcoming 0.9.8 and most likely future releases. A
This is great news. Thank you for your great work. It
Andy Polyakov writes:
Hmm, I think it would be good to create a INSTALL.W64,
I'm writing one right now. A.
Great!
Cheers,
Richard
-
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
--
Richard Levitte
bss_file.obj : error LNK2001: unresolved external symbol OPENSSL_UplinkTable
b_dump.obj : error LNK2001: unresolved external symbol OPENSSL_UplinkTable
So as you adviced I tried the following:
perl ms/uplink.pl win64a uplink.asm
ml64 -c uplink.asm
add it to APP_EX_OBJ in ntdll.mak file.
Hi!
First of all I figured it out that i should use SHLIB_EX_OBJ not
APP_EX_OBJ :))
Second if I add both uplink.obj and uptable.obj to SHLIB_EX_OBJ then I
cannot link libeay32.dll:
link /nologo /subsystem:console /opt:ref bufferoverflowU.lib
/dll /out:o
ut32dll\libeay32.dll
First of all I figured it out that i should use SHLIB_EX_OBJ not
APP_EX_OBJ :))
Keep in mind that the instructions were provided off the top of my head
and not actually tested, which is why it's so bumpy. Bear with me:-)
Second if I add both uplink.obj and uptable.obj to SHLIB_EX_OBJ then I
Hi again!
Well, no multiple $lazyN is improvement, isn't it? The above error
message doesn't make sense though. uplink.obj complains about symbol
being already defined in itself... H-m-m-m... I have to ponder over
this...
Thanks. But i have made some progress... see later in this mail.
Stop saying it works properly. It links, it passes the test, but it's
missing the functionality.
Well, functionality which I don't need.
Sorry, bit for me it's either everything or nothing. In this particular
context Applink is either there, ready to be used or not there [in which
case I'd
Hi!
I have tried to build a 64 bit DLL for AMD64 processors. Using the 64
bit compiler in the new platform SDK.
However I got the following error:
link /nologo /subsystem:console /opt:ref /dll bufferoverflowU.lib
/out:o
ut32dll\libeay32.dll /def:ms/LIBEAY32.def
11 matches
Mail list logo
