Launchpad has imported 6 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=544358.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-12-04T17:34:33+00:00 nucleo wrote: Description of problem: cryptest from cryptopp hangs up when built for fc13. cryptest is running in %check section of cryptopp.spec, so cryptopp can't be built for fc13. For fc12 cryptopp builds fine. Version-Release number of selected component (if applicable): binutils 2.20.51.0.2-8.fc13 See the same issues here: http://sourceware.org/bugzilla/show_bug.cgi?id=10856 https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303 Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/32 ------------------------------------------------------------------------ On 2009-12-09T12:09:27+00:00 Nick wrote: Hi Alec, I have imported Alan Modra's patch for PR 10856 into the devel binutils rpm. Please try using the latest release (2.20.51.0.2-9), and if you still have problems, let us know. Cheers Nick Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/33 ------------------------------------------------------------------------ On 2009-12-09T15:06:21+00:00 nucleo wrote: Hi Nick, With binutils 2.20.51.0.2-9.fc13 cryptopp test not fails. Finally cryptopp-5.6.1-0.1.svn479.fc13 built: http://koji.fedoraproject.org/koji/buildinfo?buildID=143094 Should I close this bug? Alexey Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/34 ------------------------------------------------------------------------ On 2009-12-13T21:03:18+00:00 Zooko wrote: This page on launchpad is tracking the progress of this issue through several different operating systems and open source projects that are affected by this bug. I added a link to this ticket on bugzilla.redhat.com: https://bugs.launchpad.net/fedora/+source/binutils/+bug/461303 Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/37 ------------------------------------------------------------------------ On 2010-04-21T16:53:22+00:00 Michal wrote: Notes: Changing version to 13 from 12, since wrt comment 0 it is clear that F-13 had that issue not F-12. Closing, we have update. Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/39 ------------------------------------------------------------------------ On 2012-01-11T19:58:39+00:00 Zooko wrote: If anybody reading this has the authority to change the status of tickets in launchpad, please mark this as fixed there: https://bugs.launchpad.net/fedora/+source/binutils/+bug/461303 . Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/461303/comments/45 ** Changed in: binutils (Fedora) Status: In Progress => Fix Released ** Changed in: binutils (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/461303 Title: generates-bad-code regression Status in binutils: Fix Released Status in MinGW: Unknown Status in pycryptopp: Fix Released Status in Tahoe-LAFS: Fix Released Status in binutils package in Ubuntu: Fix Released Status in libcrypto++ package in Ubuntu: Invalid Status in binutils source package in Karmic: Fix Released Status in libcrypto++ source package in Karmic: Invalid Status in binutils package in Fedora: Fix Released Bug description: g++-4.4 4.4.1-3ubuntu3 was used to build libcrypto++8. The current g++-4.4 in Karmic is g++-4.4 4.4.1-4ubuntu8. When 4.4.1-4ubuntu8 is used to build libcrypto++8 then the libcrypto++8 self-tests hang during the SHA validation. It appears that there has been a regression between g++ 4.4.1-3ubuntu3 and -4ubuntu8 such that the new one generates bad code. In addition to the libcrypto++8 self-tests hanging during SHA validation, if you then build python-pycryptopp using the libcrypto++8 lib that was built by g++ 4.4.1-4ubuntu8, then the python-pycryptopp library gets segfaults when it runs its self-tests. Here is the pycryptopp upstream buildbot showing segfaults on karmic, along with a valgrind report: http://allmydata.org/buildbot-pycryptopp/waterfall http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk/builds/11/steps/test/logs/valgrind To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/461303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
