Celestia Forums

Anybody have difficulty building this (besides me)? I'm using GCCfss 4.2.0. I get to the build of asterism.o in celengine before it dies.

In file included from ../celengine/selection.h:15,
from ../celengine/frame.h:16,
from ../celengine/observer.h:21,
from ../celengine/octree.h:18,
from ../celengine/staroctree.h:17,
from ../celengine/stardb.h:18,
from asterism.h:16,
from asterism.cpp:21:
../celengine/body.h:154: error: expected ?,? or ?...? before numeric constant
../celengine/body.h:162: error: expected ?,? or ?...? before numeric constant
../celengine/body.h:175: error: expected ?,? or ?...? before numeric constant
../celengine/body.h:177: error: ?float Body::getApparentMagnitude(const Star&) const? cannot be overloaded
../celengine/body.h:164: error: with ?float Body::getApparentMagnitude(const Star&) const?

I recently received the following information:

Your compilation error messages from the file ../celengine/body.h
occur on lines that use the identifier "sun". On Solaris,
this identifier has been commandeered as the name of a macro.
To undefine this macro, pass the command line argument
CPPFLAGS='-Usun'
to the Celestia ./configure script. Hope this helps.

--- edit ---

john Van Vliet wrote:also the 1.5.1 source will need a patch to build with gcc4.2 or 4.3 ( on my box)

or use the svn code ,that has been fixed and builds using gcc 4.3
-- for svn ---
some like me and a few others , have found that the new auto tools through an error when using the svn 's file " Makefile.cvs" to build "configure " and have had to use
" autoconf -v -i "
to make the "configure" file .

I take it you can build with the new admin folder?
cartrite

--- edit ---

Sorry, I just now noticed that you are talking about svn 4582. Save a copy of the admin folder before running svn update.
With svn 4589, this is the same for me on my openSuse 10.2 system which uses an older automake system. I didn't really test to see if there was a fps gain though. It doesn't work with makefile.cvs.

It also doesn't work with Suse 11.1 though. It does build but at the end I get a libtool error.

The admin folder was updated so it would be forward compatible with newer build tools like autoconf, automake and libtool but it doesn't look like it is going to be forward compatible enough. Time will tell.
cartrite

--- edit ---

john Van Vliet wrote:ChristTrekker have you got it working ?

Haven't had a chance to get back to this yet. Been trying to fix problems with my toolchain to get some other projects working...