Ah Great! Spaceman Spiff has worse problems!

The place to discuss creating, porting and modifying Celestia's source code.
Topic author
Spaceman Spiff
Posts: 420
Joined: 21.02.2002
With us: 22 years 9 months
Location: Darmstadt, Germany.

Ah Great! Spaceman Spiff has worse problems!

Post #1by Spaceman Spiff » 10.06.2005, 19:13

Greetings all,

I'm currently being stuffed in my personal exercise of being more self sufficient with Celestia* through Linux, i.e., compiling from a CVS snapshot, by frightfully obscure errors (well, they are to me).

I gathered from topic "Celestia Development : Configure file error" (http://celestiaproject.net/forum/viewtopic.php?t=5031) that I've reached the same point as dzastro(anon), but I don't know how to 'line up libraries'. In fact, I think I see what Fridger means about various dists changing everything about in the Linux file structure. Never mind /usr/local, my textures went in /usr/share/apps/celestia!

So I get the familiar:

Code: Select all

checking for gluLookAt in -lGLU... yes
./configure: line 25573: syntax error near unexpected token `GTK,'
./configure: line 25573: `              PKG_CHECK_MODULES(GTK, libgnomeui-2.0 gtk+-2.0 gtkglext-1.0)'


Well, it's further than the disappointing

Code: Select all

checking target system type... i686-pc-linux-gnu
./configure: line 1536: AM_INIT_AUTOMAKE: command not found
./configure: line 1537: syntax error near unexpected token `config.h'
./configure: line 1537: `AM_CONFIG_HEADER(config.h)'

I got with a CVS snapshot from 3 week ago.

So. 'What do I do?'

Ta for the inspirational topic title, Rocket Man! ;) Glad it worked.

Thinks: Hmmm, maybe we should have a new forum for Celestia I'm Stuck - Please Help Me!!!

Spiff.

*When I gwow up, I want to be a cewestia devewoper...

Avatar
t00fri
Developer
Posts: 8772
Joined: 29.03.2002
Age: 22
With us: 22 years 7 months
Location: Hamburg, Germany

Post #2by t00fri » 15.06.2005, 16:31

Spiff,

did you install the gnome package 'pkg-config'??

Also, did you install all these along with their headers ('devel' packages)??

GTK,
libgnomeui-2.0
gtk+-2.0
gtkglext-1.0

Bye Fridger

Topic author
Spaceman Spiff
Posts: 420
Joined: 21.02.2002
With us: 22 years 9 months
Location: Darmstadt, Germany.

Post #3by Spaceman Spiff » 16.06.2005, 14:24

Ah cheers, t00fri!

well, I've got no idea how to check that, so let me just learn that up... :).

Meanwhile, I've received info from a friendly, local neighbourhood Linux expert that perhaps I did A Naughty Thing.

My Linux is Mandrake 10.1. The autotools in this dist werre terribly out of date, so I downloaded and installed directly from gnu.org, ... er, bypassing the RPM database. This might be bad.

I'll need time to review what the RPM database is all about, make two steps back, etc.

Laters,

Spiff.

Avatar
t00fri
Developer
Posts: 8772
Joined: 29.03.2002
Age: 22
With us: 22 years 7 months
Location: Hamburg, Germany

Post #4by t00fri » 16.06.2005, 16:10

Spaceman Spiff wrote:Ah cheers, t00fri!

well, I've got no idea how to check that, so let me just learn that up... :).

Meanwhile, I've received info from a friendly, local neighbourhood Linux expert that perhaps I did A Naughty Thing.

My Linux is Mandrake 10.1. The autotools in this dist werre terribly out of date, so I downloaded and installed directly from gnu.org, ... er, bypassing the RPM database. This might be bad.

I'll need time to review what the RPM database is all about, make two steps back, etc.

Laters,

Spiff.


Spiff,

indeed the autotools are "holy cows"! The reason is that the various distributors often patch the corresponding databases badly to their own environments. Just uninstall the GNU's and reinstall those tools that belonged to your distribution.

In Celestia development we had quite horrible problems with the autotools at times, in order to make the configure stuff compatible with autotools from many distributors.

You can most easily check on pkg-config like so:

locate pkg-config

or in case Mandrake uses also the rpm package administration,

rpm -qa|grep config

this catches all packages with 'config' in their names.
Sometimes (SuSE) the package is called

pkgconfig
or pkg-config
...

Here is a list with all libraries, celestia-KDE needs

You generate it with the 'ldd' command, e.g. ldd /usr/local/bin/celestia

Code: Select all

        linux-gate.so.1 =>  (0xffffe000)
        libkio.so.4 => /opt/kde3/lib/libkio.so.4 (0x40018000)
        libkdeui.so.4 => /opt/kde3/lib/libkdeui.so.4 (0x40350000)
        libkdesu.so.4 => /opt/kde3/lib/libkdesu.so.4 (0x40628000)
        libkwalletclient.so.1 => /opt/kde3/lib/libkwalletclient.so.1 (0x40640000)
        libkdecore.so.4 => /opt/kde3/lib/libkdecore.so.4 (0x40651000)
        libDCOP.so.4 => /opt/kde3/lib/libDCOP.so.4 (0x4088e000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x408e2000)
        libutil.so.1 => /lib/libutil.so.1 (0x408f4000)
        libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x408f8000)
        libidn.so.11 => /usr/lib/libidn.so.11 (0x4090e000)
        libkdefx.so.4 => /opt/kde3/lib/libkdefx.so.4 (0x4093c000)
        libqt-mt.so.3 => /usr/lib/qt3/lib/libqt-mt.so.3 (0x40968000)
        libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x4105c000)
        libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x41060000)
        libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x4106a000)
        libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x4106d000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x41080000)
        libexpat.so.0 => /usr/lib/libexpat.so.0 (0x410aa000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x410c9000)
        libdl.so.2 => /lib/libdl.so.2 (0x41133000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x41137000)
        libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x41147000)
        libfam.so.0 => /usr/lib/libfam.so.0 (0x4114f000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x41157000)
        libpng.so.3 => /usr/lib/libpng.so.3 (0x41213000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x41241000)
        libGLU.so.1 => /usr/lib/libGLU.so.1 (0x41261000)
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x412dd000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x412e6000)
        libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x412fe000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x41314000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4131c000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4132c000)
        libz.so.1 => /lib/libz.so.1 (0x41428000)
        libGL.so.1 => /usr/lib/libGL.so.1 (0x41439000)
        libm.so.6 => /lib/tls/libm.so.6 (0x414a7000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x414c9000)
        libc.so.6 => /lib/tls/libc.so.6 (0x414d1000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x415e7000)
        libXxf86vm.so.1 => /usr/X11R6/lib/libXxf86vm.so.1 (0x4163a000)


Make sure /one-by-one/ that you have installed them all as well as their header packages that often have a 'devel' added to their names.

Good luck,

Bye Fridger


Return to “Development”