Description of problem: cmod models (eg phobos, deimos, amalthea) do not show up Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.start celestia 2.press enter 3.enter "phobos", press enter 4.press "g" Actual results: nothing appears Expected results: the surface of phobos should be visible Additional info: the problem is the same as for the 3ds models fixed some time ago; a workaround is to add "CXXFLAGS=-fno-strict-aliasing" in the spec file like this: %configure --with-gnome --with-lua CXXFLAGS=-fno-strict-aliasing see also bug report 171636
-fno-strict-aliasing seems to work around the issue. Several people on the celestia forums have made some progress debugging the real issue though. http://www.shatters.net/forum/viewtopic.php?t=9605 For reference, these seem to be reports of essentially the same bug: http://www.shatters.net/forum/viewtopic.php?t=8279 http://www.shatters.net/forum/viewtopic.php?t=9335 I'm rebuilding with -fno-strict-aliasing now (1.4.1-5.fc5), which should "fix" the problem, but I'm going to leave this open to remind myself to find a proper fix.
Hi, Someone (I think it was you Steven) requested that my students take a look at this. They have, unfortunately they didn't have the time to completly follow through so I've done the last step. There are actually 2 problems: 1) celestia gets build with rather non standard optflags, I'll attach a modified version of the specfile which fixes configure so that it no longer does this. This new specfile also stops autoxxx from rerunning because of applied patches. This means that the automake17 BR also is no longer necesarry 2) There is a strict alias bug in the code for which I've written a fix, which I'll also attach. Please send this upstream. Note that the modified specfile doesn't include this patch.
Created attachment 141900 [details] Spec which uses proper optflags and no longer causes rerunning of autoxxx I forgot to mention that using the proper optflags is important, because without this -fomit-frame-pointer gets passed, which results in an undebugable binary.
Created attachment 141901 [details] PATCH: fixing build without -fno-strict-aliasing
Thanks for the debugging. :-) I'm building an update for FC-5, FC-6, and devel now. I also sent the patch upstream.