On 19-10-2010 19:23, Jeffrey Walton wrote:
So I wasted my precious time preparing a patch while someone
else had already posted a patch off-list.
Lol... If you're going to throw a tantrum every time someone beats you
ta a patch, you owe us a tantrum:
WinCE patch:
http://www.mail-archive.com/ope
> So I wasted my precious time preparing a patch while someone
> else had already posted a patch off-list.
Lol... If you're going to throw a tantrum every time someone beats you
ta a patch, you owe us a tantrum:
WinCE patch:
http://www.mail-archive.com/openssl-users@openssl.org/msg61765.html
Pierr
Hi,
I was not involved in this discussion, but I wanted just to say that
patches and other development issues are discussed in the openssl-dev
list and all messages sent to r...@openssl.org are also copied to that
list not the users list. Anyone interested in OpenSSL internals should
join o
On 19-10-2010 12:32, per frykenvall wrote:
Thanks, Jakob! However, I followed Dr. Stephen Hensons advice earlier
in this thread and filed a report to the bug tracker, and got a
resolution from Andy Polyakov a week ago, based on your suggestion.
I've tested it and am fully satisfied:
[openss
Thanks, Jakob! However, I followed Dr. Stephen Hensons advice earlier
in this thread and filed a report to the bug tracker, and got a
resolution from Andy Polyakov a week ago, based on your suggestion. I've
tested it and am fully satisfied:
[openssl.org #2356] Resolved: LNK4078 and LNK4210 li
I have now created an actual patch to fix this.
It turns out to be a small pattern bug in x86_64xlate.pl
Patch attached as openssl-1.0.0a-x86_64attr.patch.
While debugging this patch I ran into an unrelated issue where nmake
would invoke nasm before the .asm file had been completely output.
Th
