Building celestia cvs

diederick76 · Post #1by **diederick76** » 04.05.2007, 13:31

Hi,

I'm trying to build Celestia from cvs, but I ssem to need some pointers. I usually know how to compile stuff, but I'm missing something here, namely the configure script. Therefore I tried creating it using autoconf, but that resulted in:

configure.in:70: error: possibly undefined macro: AM_INIT_AUTOMAKE
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:71: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:73: error: possibly undefined macro: AM_PO_SUBDIRS
configure.in:74: error: possibly undefined macro: AM_GNU_GETTEXT
configure.in:95: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
configure.in:96: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.in:117: error: possibly undefined macro: AC_MSG_RESULT
configure.in:184: error: possibly undefined macro: AM_CONDITIONAL
configure.in:224: error: possibly undefined macro: AC_CHECK_COMPILERS
configure.in:283: error: possibly undefined macro: AM_GCONF_SOURCE_2
configure.in:326: error: possibly undefined macro: AC_ENABLE_SHARED
configure.in:327: error: possibly undefined macro: AC_ENABLE_STATIC
configure.in:330: error: possibly undefined macro: AM_KDE_WITH_NLS
configure.in:333: error: possibly undefined macro: AC_PATH_KDE

I read the manpage on autoconf, but this is the first time I use that program, so can anyone tell me what I'm doing wrong here?

Thanks for any help,
Diederick

Post #2by **t00fri** » 04.05.2007, 14:32

Nooo...

simply type

+++++++++++++++++
make -f Makefile.cvs
+++++++++++++++++

that starts the autotools and generates the configure script.

Bye Fridger

diederick76 · Post #3by **diederick76** » 04.05.2007, 18:48

When I do that, I get this:

# make -f Makefile.cvs
This Makefile is only for the CVS repository
This will be deleted before making the distribution

*** Creating acinclude.m4
*** Creating aclocal.m4
acinclude.m4:3345: the serial number must appear before any macro definition
acinclude.m4:3390: the serial number must appear before any macro definition
acinclude.m4:3435: the serial number must appear before any macro definition
acinclude.m4:5560: the serial number must appear before any macro definition
/usr/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
/usr/share/aclocal/gtk.m4:7: run info '(automake)Extending aclocal'
/usr/share/aclocal/gtk.m4:7: or see http://sources.redhat.com/automake/auto ... ng-aclocal
configure.in:283: warning: macro `AM_GCONF_SOURCE_2' not found in library
*** Creating configure
configure.in:283: error: possibly undefined macro: AM_GCONF_SOURCE_2
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
make[1]: *** [cvs] Error 1
make: *** [all] Error 2

I read the text about extending acolocal, but I'm not a c programmer, so that didn't help. Are the warning and error mentioned here related? What can I do?

Thanks,
Diederick

Post #4by **t00fri** » 04.05.2007, 18:53

Then either something is not properly installed or you use an outdated set of autotools.

The developers are running the make -f Makefile.cvs command on a 1/day rate ;-)

without any problems.

Perhaps you got something wrong by your previous "handicrafting" ? What versions of the autotools are you using? What Celestia version?

Bye Fridger

diederick76 · Post #5by **diederick76** » 04.05.2007, 19:40

t00fri wrote:Perhaps you got something wrong by your previous "handicrafting" ? What versions of the autotools are you using? What Celestia version?

I use autoconf version 2.61. It was compiled using --prefix=/usr.

I redid the checkout, to rule out any possibility of problems arising due to my previous handicrafting, like this:

# cvs -z3 -q -d :pserver:anonymous@celestia.cvs.sourceforge.net:/cvsroot/celestia co celestia

but I still get the same error. Did I checkout the right version?

Thanks for helping me,
Diederick.

Post #6by **t00fri** » 04.05.2007, 20:27

One problem with the autotools is that error messages are sometimes quite misleading. It might well be that you did not install all required libraries and/or devel packages (headers etc) .

Did you succeed to compile the celestia sources from your Linux distributor?? That should be a good exercise before trying CVs.

Bye Fridger

diederick76 · Post #7by **diederick76** » 04.05.2007, 21:02

My distro is Crux (http://crux.nu), which is a source based distro. Everything I install I have to compile myself, which means that there are no separate devel packages. When I install something, I also get the header files. Repositories contain scripts which install dependencies and do the configuring/compiling for me and all installed files are registered into a database for easy package management.

There is a celestia 1.4.1 package available, but that doesn't compile, because I use gcc 4.1.2. This is exactly why I need the cvs version, for which there is no package for my distro available.

Can you tell me what packages Celestia needs? I have am using nvidia driver version 9755.

Post #8by **Christophe** » 04.05.2007, 21:57

Do you have GTK and GConf? those are required to build the configure script even if you only want to build the KDE frontend after that.

diederick76 · Post #9by **diederick76** » 04.05.2007, 22:38

Gconf was missing. After installing it, Celestia build and now it runs perfectly. Thanks!:D

Diederick.

Post #10by **t00fri** » 04.05.2007, 22:42

diederick76 wrote:Gconf was missing. After installing it, Celestia build and now it runs perfectly. Thanks!:D

Diederick.

...as your error report said right from the beginning:

configure.in:283: warning: macro `AM_GCONF_SOURCE_2' not found in library

Usually, there is some item missing ;-)

as I suggested.

Good that it works now.

Bye Fridger