On Tue, May 21, 2013 at 11:00 AM, Viktor Dukhovni
wrote:
> If so, this is a Windows Perl bug IMHO. The parent should wait
> for the child to exit with close(STDOUT) in either scenario.
> Any special treatment of STDOUT should be reset after
>
> open STDOUT,"|cmd";
>
> in such a way as to
On Tue, May 21, 2013 at 10:14:27AM -0600, Phillip Hellewell wrote:
> Good news, I found the bug! I got thinking, why is x86_64-gf2m the
> only one giving me a problem? So I compared x86_64-gf2m.pl to the
> others and found that it has this line:
> open STDOUT,"| \"$^X\" $xlate $flavour $outp
Good news, I found the bug! I got thinking, why is x86_64-gf2m the
only one giving me a problem? So I compared x86_64-gf2m.pl to the
others and found that it has this line:
open STDOUT,"| \"$^X\" $xlate $flavour $output";
whereas the others have this:
open OUT,"| \"$^X\" $xlate $flavour $
I forgot to mention, I am using perl.exe version 5.16.3 and nasm.exe
version 2.10.07.
Phillip
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@ope
On Tue, May 21, 2013 at 9:08 AM, Phillip Hellewell wrote:
> But when executed from my build script (a batch file), it runs into
> problems.
Here is a copy of my build script. Can anyone spot a problem with it?
@echo off
if "%1"=="" goto buildall
setlocal
cd /d "%~dp0.."
@call target\dependency
On Tue, May 21, 2013 at 5:33 AM, Dr. Stephen Henson wrote:
> Just tried it myself with Visual Studio 2012, nasm version 2.10.07 and it
> compiles with no problems for me. I also tried it without nasm (i.e. ml64) and
> that worked OK too.
Ok, this is very helpful to know that it is working for oth
On Mon, May 20, 2013, Phillip Hellewell wrote:
> On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell wrote:
> > Should I try to patch it myself?
>
> FYI, the linker error is occurring because nasm is failing with a ton
> of errors on x86_64-g2m.asm, I think maybe because it is creating the
> wron
On 5/21/2013 2:04 AM, Phillip Hellewell wrote:
On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell wrote:
Should I try to patch it myself?
FYI, the linker error is occurring because nasm is failing with a ton
of errors on x86_64-g2m.asm, I think maybe because it is creating the
wrong type of a
It might be better if you specify how you set up your environment, what
versions of perl and nasm you used, and what sequence of commands you used.
I usually do a cut-down static build in an environment based on the Windows
Driver Kit, and I've built 1.0.1e using nasm without problems. I just tr
On Mon, May 20, 2013 at 1:12 PM, Phillip Hellewell wrote:
> Should I try to patch it myself?
FYI, the linker error is occurring because nasm is failing with a ton
of errors on x86_64-g2m.asm, I think maybe because it is creating the
wrong type of asm.
So I tried masm instead, and it is working s
On Thu, May 16, 2013 at 5:27 PM, Phillip Hellewell wrote:
> But do I have to sacrifice performance to be able to upgrade to 1.0.1?
Anyone? Can I be the only one in the whole world who wants to build
openssl on Windows 64-bit with optimized assembly routines?
Should I try to patch it myself? Sh
I'm trying to upgrade from 0.9.8y to 1.0.1e, but I'm getting this linker error.
link /nologo /subsystem:console /opt:ref /debug /dll
/out:out32dll\libeay32.dll /def:ms/LIBEAY32.def
@C:\Users\PHELLE~1\AppData\Local\Temp\nm6C7E.tmp
Creating library out32dll\libeay32.lib and object out32dll\libea
12 matches
Mail list logo
