Description of problem: See scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2204246 Version-Release number of selected component (if applicable): hedgewars-0.9.12-2.fc13 How reproducible: Happened using rpmbuild locally on an f13 system and with a koji scratch build. Additional info: I was looking at seeing what it would take to have the package install a dedicated server for use at the next community gaming session. If I get time, I'll be looking at this bug myself over the next week. My current guess is that this is a DSO linking issue that didn't get categorized as such because cmake hides the low level messages by default. My next step is building using verbose mode to get a better idea of what is actually failing.
One problem seems to be at some time people were using -Nu as a pascal compiler option and it no longer seems to be valid for fpc. I think the option was used to specify an unroll loops optimization.
Created attachment 415997 [details] Remove the -Nu option So it looks like what happened is either the -Nu option was dropped from fpc or it got more strict about handling unknown options. Not using this option gets the build to complete again. I probably be doing an RFE about the dedicated server, so you might not want to rush this change into a new build unless you need it for something else.
Created attachment 415998 [details] Patch to get the spec file to use the no -Nu patch
hedgewars-0.9.12-3.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/hedgewars-0.9.12-3.fc13
hedgewars-0.9.12-3.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update hedgewars'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/hedgewars-0.9.12-3.fc13
hedgewars-0.9.12-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.