Celestia Forums

Hi guys,

just tried to build Celestia Qt and ran into the following error message:


And QTCreator marked the following:


Was building on Fedora 11 with latest kernel (just updated) and with latest Qt version. Clean SVN, just created the directory and checked out all files.
Oh yeah, and started Qt Creator and opened "celestia.pro", then selected "Release" and "Build".

Hope someone can help me and tell me what I did wrong.

Regards,

Guckytos

Christian,

you left out the most important info: do you have config.h located in the celestia root dir or not??
If not simply type 'touch config.h'. I don't have the slightest probs with compilation of Celestia-qt under ANY OS.

Fridger

Hi Fridger,

the tipp with "touch config.h" did the trick and allowed me to start building. Unfortunately this only led to more warnings and errors.
First I got 4 warnings and 18 errors.

After I used your tipp on a missing File called "SpiceUsr.h" in the directory "celephem" I came down to 17 errors.
Most of them are of the type "xxx was not defined in this validity range (roughly translated)"
I have a screenshot of the messages attached if that helps.

And yes, I am a complete noob in these things without really knowing what I am doing, but finding the results and learning a bit more quite interesting.

Regards,

Guckytos

Christian,

Deinen Fehler bzgl SpiceUsr.h verstehe ich ueberhaupt nicht. Dieses header File gehoert doch ins

windows/inc/spice

sub-directory, aber nicht nach 'src/celephem'! Ausserdem darfst Du nicht einfach fehlende files mit 'touch <file>' creieren und auf NULL Inhalt setzen. Das geht nur mit config.h, da es fuer Celestia-Qt i.w. nicht verwendet wird.

Du solltest als Erstes mal lernen wie man mit qmake und celestia.pro umgeht. Sonst wird das wohl nichts.

Fridger

PS: Oh, sorry: just noted that I wrote in German, our usual way of communicating via PM. I am too lazy to rewrite the stuff in English

Hi Fridger,

you are probably right. First I have to learn a bit more about the different files and program languages.
My fast success in building Celestia on Windows could be the culprit why I thought it would be just as easy with Linux and Qt.

Thanks for any help.

Regards,

Guckytos

Christian,

it's important to use the latest SVN version and also a solid Qt 3.5.x installation.

Then everything should be in the correct directories and Qt-Creator (1.3.x) almost works autmatically with an up-to-date celestia.pro. You really don't have to fiddle around, if your installation is basically correct. Note that you need a full Qt installation, not just the run-type version.

I advice to checkout a separate Celestia-Qt package. Otherwise, there may be interferences, if you use the same sources BOTH for building the Qt and NON-Qt versions. Note that the base directory for the Qt compilation is the celestia/src directory, while for Windows/Linux it's the Celestia-root directory.

Fridger

--- edit ---

--- edit ---

--- edit ---

--- edit ---

john Van Vliet wrote:8O ???
i do tend to ramble

I'm waiting for Christian's reply...

john Van Vliet wrote:1)
i assume that celestia Gnome svn builds
autoreconf -v -i
-- my code, yours will be a bit different --
./configure --prefix=/usr/opt/GTK_Celestia --with-gnome -with-cspice-dir=/DATA/cspice -program-prefix=GTK
make
su
-- with NO "-" no dash -----
make install

Correct, Celestia Gnome build runs smoothly now.

2)
the kde qt3 ???? dos not need to build for fedora 13 ( kde3.5 is not to well supported on fedora 13 )
BUT you WILL need to make a "config.h" for QT-Creator
deleat the old one
-- or BETTER YET if you are reusing the same folder as the gnome build run

Code: Select all

su
make distclean

or recopy your svn download folder to your WORKING FOLDER
( it is a very good practice to get into of NOT building in the svn download folder )

3)
clean build folder
run

Code: Select all

autoreconf -v -i
./configure --with-kde


that makes a "config.h" file
you will ALSO need to edit the "config.h" file . Mostly double check it

Okay, created a new working folder from a fresh SVN download. Then ran autoreconf, then tried ./configure --with-kde but only got the following error

Tried it then with the following ./configure --> resulting in the same error.


I think as usual I messed the syntax up, but I am not sure where.
The error log does not really tell me too much at the moment, but for all those you know what it means it is attached.

also for fedora 13 the GL headers in "thirdparty/glew" are most likely DIFFERENT than the ones in /usr/include/GL
make surl the upto date fedora 13 files are installed

Code: Select all

yum search gl


and install the glew ,glxew ,wglew and the matching -devel

Nice one here too with the GLEW-devel package missing, even when I thought I had all devel packages with groupinstall installed.

So until at least the config.h is being built I am stuck (again). But the weekend just started and the weather outside is: Raining cats and dogs with the tendency to stay like this

--- edit ---

john Van Vliet wrote:from the config log it looks like a perl check error
line 2130 it starts
but

So until at least the config.h is being built I am stuck (again). But the weekend just started and the weather outside is: Raining cats and dogs with the tendency to stay like this

configure DID get far enough to make a config.h file ?

Good morning John,

I was not precise enough. configure does not get far enough to finish the config.h, it stops with this error:

--- if not ---

well we will just have to make one
use the gnome one and undefine gnome settings
############
/* Use Cairo for Splash */
/* #undef CAIRO */
################
/* Use Gnome Flag */
/* #undef GNOME */
#############
might do it

Will try that later today and keep you posted.

Nice one here too with the GLEW-devel package missing, even when I thought I had all devel packages with groupinstall installed.

just installing a group like " Gnome Desktop development " or the "Development Tools" "Development Library’s"
will NOT install every single -devel rpm there is ( about 30+ Gig's - yes Gig 's - more )

mixing header files with different lib's is not a good idea so if at all possible USE the ones in the fedora reop

and fedora tends to be very picky with this seeing as it tends to be VERY cutting edge
That is one of the quarks of using fedora ( besides the clean reinstalls every 6 months or using "preupgrade" if you do not have to much installed from source and from 3d party repos and a /boot partition that is 1 gig + in size )

Yep, I just remembered, that I had something similar happening, when trying to build Gnome and config always failing. Turned out that yum did not install the gtkglex1-devel package. But the error message was first pointing me into the wrong direction, until I found the solution here in the forum.

Well, before upgrading from Fedora 11 to 13 I did take a look at Ubuntu, but somehow I didn't like it too much and decided to stay with Fedora. Could be a stupid decision for a newbie, but hey, I am who I am

--- edit ---

Okay,

and on goes the (endless?) journey.

Yes, with "touch config.h" I get Qt to start building and it is running quite a good time, before exiting with and png error.

I checked the libpng in /usr/include/png.h and it is pointing to /usr/include/libpng12/png.h

But I am not sure that the Qt output is the same error as stated by you in the Bug section of the forum. See attached error log



The reason, why I believe it is not the same error is that is happening in icons.ccp

Regards,

Guckytos

--- edit ---

john Van Vliet wrote:i just downloaded the zip and will look at it tomorrow seeing as it is 4AM
took a quick look
a linker error fun, fun,fun

may or may not work ( code is that way ??? )
/usr/lib/libpng12.so.0
is there a link called " /usr/lib/libpng.so" that points to libpng12.so.0
if not make one ( or repoint it from libpng14 )
then run

Code: Select all

 su -
ldconfig

see " man ldconfig " and "ldconfig --help "

in qt creator run " clean ALL " then rebuild all

Okay John,

I just checked. I have:

"/usr/lib/libpng.so" pointing to "/usr/lib/libpng12.so"
and "/usr/lib/libpng12.so" is then pointing to "/usr/lib/libpng12.so.0.44.0"

But there also exists a "/usr/lib/libpng12.so.0" that also points to "/usr/lib/libpng12.so.0.44.0"

Should I then also run ldconfig? I mean the configuration for most other stuff seems to work.

BTW: I am not sure how to create or repoint a link (especially the repointing). Could you give me a pointer on where to find such crucial basic info? I tried to search, but that seems to basic for where I was looking.
Would this be the correct code for creating a link?

Regards,

Guckytos

--- edit ---