When Ubuntu recently upgraded from GNU binutils 2.19.91.20091006-0ubuntu1 to 2.19.91.20091014-0ubuntu1 this broke the build of Crypto++ 5.6.0 in such a way that building Crypto++ with the new binutils results in indefinite hangs with max CPU usage or seg faults. Here is the bug report at launchpad which includes the history of me figuring out exactly which version of which tool introduced this change and also has links to the pycryptopp buildbot which shows Crypto++ 5.6.0 as built with the new binutils getting a segfault. The buildbot also has a valgrind report. The launchpad ticket also has links to the diffs between the most recent succeeding version of binutils and the earliest failing version, but I don't know enough about binutils to spot the problem.
If someone out there knows how to help, that would be great. In the meantime, at least be aware that you shouldn't upgrade to Ubuntu 9.10 (due to be released tomorrow) if you want to build Crypto++ 5.6.0! Regards, Zooko --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
