On Oct 27, 9:40 am, "Wei Dai" <[email protected]> wrote: > The error is clearly occurring within the SHA256 inline assembly code. But I > have no idea what the (fairly large) binutil patch is doing. How can we find > out who submitted the the binutil patch and contact him or her?
I've posted to https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303 asking that question. I suppose the patch came from "upstream" binutils, i.e. the Ubuntu folks acquired the patch from the binutils folks, but I'm not sure how to trace its exact provenance. > I can also look at this in the debugger and see if I can fix it in Crypto++ > code. Can you either give me a shell account on a machine that can reproduce > this, or tell me how to reproduce this, starting with a blank VMware > instance? To reproduce: Install Ubuntu Karmic Koala (release candidate or final release) Get the Crypto++ 5.6.0 source code run "make" run "cryptest.exe v" > Until this is fixed, you can try to work around it by disabling the SHA256 > (or all) assembly code. Thanks for the work-around idea. Maybe I could have my build script test the version of the GNU assembler and disable ASM if it is the known-bad version. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
