configure script missing from CVS (unlikely)

[berkowski]

from README

INSTALLING IN UNIX
------------------
Type "./configure --help" for a list of options. The basic commands are shown
below. For more detailed information, refer to the INSTALL file.

From INSTALL

OK, assuming you've collected all the necessary libraries, here's
what you need to do to build and run Celestia:

./configure --with-INTERFACE [*]
make
make install

but after downloading from CVS. . . .

Code: Select all

find -iname  '*config*'
./src/celestia/res/config.bmp
./src/celestia/configfile.h
./src/celestia/configfile.cpp
./admin/config.pl
./admin/configure.in.min
./admin/config.guess
./admin/config.sub
./admin/configure.in.bot.end
./configure.in
./config.guess
./config.sub


so where's my configure script?

[t00fri]

so where's my configure script?

seems to be your first CVS experience...

Type
make -f Makefile.cvs

in the Celestia root directory, which does a number of things including generation of what you were looking for...

Bye Fridger

[berkowski]

seems to be your first CVS experience...

Hense the "(unlikely)" Many thanks!
--edit---
While you're around, I've run into the same problem as this guy http://shatters.net/forum/viewtopic.php?t=6714&highlight=includearts

tried --without-arts and --with-arts=no with the same result.

[t00fri]

seems to be your first CVS experience...

Hense the "(unlikely)" Many thanks!
--edit---
While you're around, I've run into the same problem as this guy http://shatters.net/forum/viewtopic.php?t=6714&highlight=includearts

tried --without-arts and --with-arts=no with the same result.

Yes, I first found out about this trouble with ARTS in case of the gtk/gnome CVS compile and reported it to the Celestia developer's list. It was confirmed by other developers.


Here is a workaround that I did for myself. It worked for me.

I copy my email to the developers list from Feb 26 2005:

I use the latest KDE supplented by SuSE: 3.3.2 along with their provided, adapted autotools:
automake-1.9.3-4
autoconf-2.59-79

The first round of ./configure runs always OK, but then when I hit 'make', the admin/missing script is started and automatically runs those configure tools once more. At this point the error

' conditional "include_ARTS" was never defined.'

arises.

Here is a fix in configure.in (no idea whether this makes any sense, but it alsways works for me)

AC_ARG_WITH([gnome],
AC_HELP_STRING([--with-gnome], [Use Gnome for an enhanced GUI]),
ui_gnome="yes"; ui_gtk="yes"; ui_glut="no"; ui_kde="no",
ui_gnome="no")
<--------------------------
if (test "$ui_gnome"="yes"); then
include_ARTS_TRUE=
include_ARTS_FALSE='#'
fi
<---------------------------

This avoids later the error in ./configure that tests
this:

if test -z "${include_ARTS_TRUE}" && test -z "${include_ARTS_FALSE}"; then
{ { echo "$as_me:$LINENO: error: conditional "include_ARTS" was never defined
.
Usually this means the macro was only invoked conditionally." >&5
echo "$as_me: error: conditional "include_ARTS" was never defined.
Usually this means the macro was only invoked conditionally." >&2;}
{ (exit 1); exit 1; }; }
fi

Bye Fridger

Good luck,...

Bye Fridger

[berkowski]

Great, thanks again. Just need to get around segfaults with ati-drivers now

[t00fri]

Great, thanks again. Just need to get around segfaults with ati-drivers now

That may indeed be more problematic, depending on your model. Under Linux, the latest drm 'radeon' drivers contained in xorg-6.8.2, work quite well even with most problematic ATI cards, including ATI 9200SE. These drivers are somewhat slower, however, than the native ATI fglrx drivers. The latter segfaulted persistently with various ATI cards for a long time. Perhaps the very latest one works now, since ATI use Celestia to test eliminate their driver bugs more recently!

The problems with ATI cards are mostly due to bugs in the ATI drivers, not in Celestia.

Bye Fridger