Linux KDE build

[Boux]

I do not know whether somebody is maintaining the CVS tree for Linux...
I has become a bit complicated to build Celestia as many files necessary for building are looking as they are completely obsolete (can be GCC, libtools, makefiles, uncontrolled dependencies - lua, spice, theora, etc.), with regard to the latest distributions.
It is not a big issue for me to spot the many dead ends and edit the relevant files in the tree to end up with a successful build.
It can be a real pain for those who have little clue about the changing prerequisites for the build environment.
I will make available a KDE/GCC 4.1 and above, lua 5.0, Nvidia Glx executable on my ftp, built from the latest workable CVS.
If there is some interest, I will maintain this service.
The latest executable is available there:

http://jmmi.club.fr/celestia/linux/celestia

Please check your Celestia environment for required libraries and dependencies:

Code: Select all

[root@localhost bin]# ldd celestia
        linux-gate.so.1 =>  (0xb7f6a000)
        liblualib.so.5.0 => /usr/lib/liblualib.so.5.0 (0xb7f56000)
        liblua.so.5.0 => /usr/lib/liblua.so.5.0 (0xb7f3e000)
        libkio.so.4 => /usr/lib/libkio.so.4 (0xb7bbb000)
        libkdeui.so.4 => /usr/lib/libkdeui.so.4 (0xb78a7000)
        libkdesu.so.4 => /usr/lib/libkdesu.so.4 (0xb7890000)
        libkwalletclient.so.1 => /usr/lib/libkwalletclient.so.1 (0xb787e000)
        libkdecore.so.4 => /usr/lib/libkdecore.so.4 (0xb760c000)
        libDCOP.so.4 => /usr/lib/libDCOP.so.4 (0xb75d5000)
        libresolv.so.2 => /lib/libresolv.so.2 (0xb75a6000)
        libutil.so.1 => /lib/libutil.so.1 (0xb75a2000)
        libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xb7587000)
        libidn.so.11 => /usr/lib/libidn.so.11 (0xb7556000)
        libkdefx.so.4 => /usr/lib/libkdefx.so.4 (0xb7528000)
        libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0xb6e7b000)
        libmng.so.1 => /usr/lib/libmng.so.1 (0xb6e0f000)
        liblcms.so.1 => /usr/lib/liblcms.so.1 (0xb6dd7000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb6dd2000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb6dc8000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb6dc3000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb6dc0000)
        libXft.so.2 => /usr/lib/libXft.so.2 (0xb6dac000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb6d7e000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb6d09000)
        libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb6bdc000)
        libpthread.so.0 => /lib/i686/libpthread.so.0 (0xb6bc9000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb6bc0000)
        libfam.so.0 => /usr/lib/libfam.so.0 (0xb6bb8000)
        libacl.so.1 => /lib/libacl.so.1 (0xb6bb1000)
        libattr.so.1 => /lib/libattr.so.1 (0xb6bab000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb6b85000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb6b62000)
        libGLU.so.1 => /usr/lib/libGLU.so.1 (0xb6ae0000)
        libXmu.so.6 => /usr/lib/libXmu.so.6 (0xb6ac9000)
        libXt.so.6 => /usr/lib/libXt.so.6 (0xb6a72000)
        libSM.so.6 => /usr/lib/libSM.so.6 (0xb6a68000)
        libICE.so.6 => /usr/lib/libICE.so.6 (0xb6a4f000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0xb6a47000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0xb6a44000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb6a3e000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb6a2b000)
        libGL.so.1 => /usr/lib/libGL.so.1 (0xb6996000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0xb6987000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0xb6888000)
        libdl.so.2 => /lib/libdl.so.2 (0xb6884000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb67a0000)
        libm.so.6 => /lib/i686/libm.so.6 (0xb677b000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb676f000)
        libc.so.6 => /lib/i686/libc.so.6 (0xb6642000)
        /lib/ld-linux.so.2 (0xb7f6b000)
        libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0xb5cd0000)
        libnvidia-tls.so.1 => /usr/lib/tls/libnvidia-tls.so.1 (0xb5cce000)


If this is useful, it could be considered for a sticky.
REMINDER: this a build for KDE 3.5.xx, Xorg 7.xx, GCC 4.1.xx, lua 5.xx with latest Nvidia driver ONLY.
Enjoy

[selden]

Boux,

My understanding is that Celestia v1.5.0 uses Lua v5.1, not 5.0.

[Boux]

Hi, Selden
Actually, it works with both.
There is a fallback trick, well, a ugly hack.
For some reasons, I keep lua 5.0 on my system in parallel with 5.1 for compatibility with another project.
Celestia 1.5.xx builds without a hiccup.
Have a look at the ldd output...

[selden]

Supposedly, however, there are incompatibilities between the two versions of Lua. Since the Windows version of Celestia v1.5.0 includes Lua v5.1, I suspect that there will be scripts that won't work with copies of Linux Celestia that have been built with Lua v5.0. This could result in quite a bit of confusion.

[t00fri]

I do not know whether somebody is maintaining the CVS tree for Linux...

Boux,

yes Christophe usually keeps Celestia-KDE in pretty good status. I recompile Celestia-KDE whenever there was a new commit to CVS and never have any problems with it. Notably since Toti eliminated most compiler warnings. I am using Gcc 4.1.x and KDE 3.5.5. Also Celestia-GTK and Celestia-Gnome compile without any problems from CVS. The latter are well maintained by Pat Suwalsky.

Of course I use Lua 5.1 and Spice.

(SuSE 10.1 + MANY updates via 'smart').

Bye Fridger

[Boux]

Actually, I was not talking about KDE specifically.
I was talking about the files requested by autoconf etc.
On this brand new Mandriva 2007 install, I had to replace a number of them with more recent ones from libtool.
Anyway, a new build from latest CVS for KDE is available in my signature.

[Christophe]

Actually, I was not talking about KDE specifically.
I was talking about the files requested by autoconf etc.
On this brand new Mandriva 2007 install, I had to replace a number of them with more recent ones from libtool.

I'm a bit surprised. Doesn't Celestia build with autoconf 2.5 and automake 1.8?

[Boux]

Actually, I was not talking about KDE specifically.
I was talking about the files requested by autoconf etc.
On this brand new Mandriva 2007 install, I had to replace a number of them with more recent ones from libtool.

I'm a bit surprised. Doesn't Celestia build with autoconf 2.5 and automake 1.8?

It did not build out of the box on this system (automake 1.9.6 and autoconf 2.59)

[t00fri]

Actually, I was not talking about KDE specifically.
I was talking about the files requested by autoconf etc.
On this brand new Mandriva 2007 install, I had to replace a number of them with more recent ones from libtool.

I'm a bit surprised. Doesn't Celestia build with autoconf 2.5 and automake 1.8?

It did not build out of the box on this system (automake 1.9.6 and autoconf 2.59)

Boux,

I am using automake 1.96 and autoconf 2.59 and Celestia-kde builds out of the box from CVS. So it seems your initial problems were related to Mandriva and not to Celestia.

Bye Fridger

[Boux]

Actually, I was not talking about KDE specifically.
I was talking about the files requested by autoconf etc.
On this brand new Mandriva 2007 install, I had to replace a number of them with more recent ones from libtool.

I'm a bit surprised. Doesn't Celestia build with autoconf 2.5 and automake 1.8?

It did not build out of the box on this system (automake 1.9.6 and autoconf 2.59)

Boux,

I am using automake 1.96 and autoconf 2.59 and Celestia-kde builds out of the box from CVS. So it seems your initial problems were related to Mandriva and not to Celestia.

Bye Fridger

I am pretty sure you are mostly right.
I choose Mandriva only because it is the only distrib which would recognize properly most of my hardware combination (C2 duo i965+ich8r+jmicron raid).
By the way, I tried Suse, Ubuntu, Fedora and a couple others, more obscure distribs.
On a sidenote, I think I have spotted a problem with config.sub which looks like it is puzzled by this very hardware config.
There are a lot of threads at many Linux forums about the issue.
The hardware is a little step ahead of the os, apparently.
Even 6.18 kernels and above, which were supposed to clear these issues have problems with this latest intel stuff.
It is not a big deal, anyway, after some hacking and tweaking, Celestia builds happily.
That is the Linux fun after all.
One can easily go have a look under the hood and tune and customize the engine so that it runs according to one's need!

[Boux]

A new build is available (link in sig).
It has been built for KDE with Theora and Lua 5.1.1 support.
It also runs with Gnome on this rig without a glitch.