Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 539227 - FTBFS cryptopp-5.6.0-4.fc13
Summary: FTBFS cryptopp-5.6.0-4.fc13
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: cryptopp
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On: 544358
Blocks: F13FTBFS
TreeView+ depends on / blocked
 
Reported: 2009-11-19 17:19 UTC by FTBFS
Modified: 2013-03-13 05:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-09 14:19:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log (35.39 KB, text/plain)
2009-11-19 17:19 UTC, FTBFS 		no flags Details
build.log (386.81 KB, text/plain)
2009-11-19 17:19 UTC, FTBFS 		no flags Details
mock.log (960 bytes, text/plain)
2009-11-19 17:19 UTC, FTBFS 		no flags Details
root.log (37.91 KB, text/plain)
2009-11-19 17:19 UTC, FTBFS 		no flags Details
build.log (378.26 KB, text/plain)
2009-11-19 17:19 UTC, FTBFS 		no flags Details
mock.log (967 bytes, text/plain)
2009-11-19 17:19 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2009-11-19 17:19:17 UTC 
cryptopp-5.6.0-4.fc13.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.
Comment 1 FTBFS 2009-11-19 17:19:20 UTC 
Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
Comment 2 FTBFS 2009-11-19 17:19:22 UTC 
Created attachment 372273 [details]
root.log

root.log for i386
Comment 3 FTBFS 2009-11-19 17:19:24 UTC 
Created attachment 372274 [details]
build.log

build.log for i386
Comment 4 FTBFS 2009-11-19 17:19:26 UTC 
Created attachment 372275 [details]
mock.log

mock.log for i386
Comment 5 FTBFS 2009-11-19 17:19:27 UTC 
Created attachment 372276 [details]
root.log

root.log for x86_64
Comment 6 FTBFS 2009-11-19 17:19:29 UTC 
Created attachment 372277 [details]
build.log

build.log for x86_64
Comment 7 FTBFS 2009-11-19 17:19:30 UTC 
Created attachment 372278 [details]
mock.log

mock.log for x86_64
Comment 8 nucleo 2009-11-26 02:26:07 UTC 
Finally I have found the reason why cryptest crashes.
There was in cryptopp 5.6.0 patented code MARS which was removed from Fedora 
and I was trying to build svn r479 withoutMARS  too.
When I have build with mars cryptest not crashes and not hangs up any more.

http://koji.fedoraproject.org/koji/taskinfo?taskID=1831292

There is in cryptopp Readme.txt from svn 479:
5.6.1 - switched to a public domain implementation of MARS

Is there any legal issues to not include now MARS code in Fedora after is was 
moved to public domain?
Comment 9 nucleo 2009-11-26 03:14:57 UTC 
Looks like other build of svn 479 not fixes this issue.
http://koji.fedoraproject.org/koji/taskinfo?taskID=1831344
cryptest crashes here.
I don't know why it happens.
Comment 10 nucleo 2009-11-26 03:48:51 UTC 
See this discussion in Crypto++ Users mailing list

http://groups.google.com/group/cryptopp-users/browse_thread/thread/7ce734e479586640
Comment 11 nucleo 2009-12-09 14:19:34 UTC 
After fixing of bug 544358 cryptopp builds now

See cryptopp-5.6.1-0.1.svn479.fc13

http://koji.fedoraproject.org/koji/buildinfo?buildID=143094

Build logs:
http://kojipkgs.fedoraproject.org/packages/cryptopp/5.6.1/0.1.svn479.fc13/data/logs/i686/build.log
http://kojipkgs.fedoraproject.org/packages/cryptopp/5.6.1/0.1.svn479.fc13/data/logs/x86_64/build.log

root logs:
http://kojipkgs.fedoraproject.org/packages/cryptopp/5.6.1/0.1.svn479.fc13/data/logs/i686/root.log
http://kojipkgs.fedoraproject.org/packages/cryptopp/5.6.1/0.1.svn479.fc13/data/logs/x86_64/root.log
Note You need to log in before you can comment on or make changes to this bug.