Page 1 of 1
GTK error
Posted: 17.09.2006, 20:03
by Brendan
I compiled the CVS Celestia on Fedora Core 5 with gcc 4.1.1 and got this
Code: Select all
(celestia:15492): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion `width >= -1' failed
with both the gnome and gtk builds when I tried running them. It showed a progress bar with an error icon that appears to be represent a missing image and then exited.
The system is a Fedora Core 5 one with AMD64 and a GeForce 7600 GS.
Posted: 18.09.2006, 13:53
by suwalski
This one's easy!
Make certain you "make install" so that the program can find its data files.
A current project of mine is to re-write the file loader classes so that this will be more obvious.
Posted: 18.09.2006, 23:31
by Brendan
This error appeared after doing a make install.
Posted: 18.09.2006, 23:42
by suwalski
That's rather impossible, if you're using an up-to-date CVS checkout. Make sure you're using automake-1.9.
Make sure you do have a recent checkout. Last week I redid portions of the Makefiles to work with automake-1.9, specifically a problem with ${prefix}.
Posted: 18.09.2006, 23:57
by t00fri
suwalski wrote:That's rather impossible, if you're using an up-to-date CVS checkout. Make sure you're using automake-1.9.
Make sure you do have a recent checkout. Last week I redid portions of the Makefiles to work with automake-1.9, specifically a problem with ${prefix}.
Why should he use automake 1.9? I use version 1.7.6 and things work fine. Also users should NOT be required to always use the latest software...Unlike Windows, Linux applications still do not offer in general an auto-update service
[Thunderbird/Firefox are exceptions]
Bye Fridger
Posted: 19.09.2006, 10:10
by Brendan
I have autoconf 2.59-7 and automake 1.9.6-2. When running autoconf, I get this:
Code: Select all
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:211: error: possibly undefined macro: AC_CHECK_COMPILERS
configure.in:260: error: possibly undefined macro: AM_CONDITIONAL
configure.in:270: error: possibly undefined macro: AM_GCONF_SOURCE_2
configure.in:313: error: possibly undefined macro: AC_ENABLE_SHARED
configure.in:314: error: possibly undefined macro: AC_ENABLE_STATIC
configure.in:317: error: possibly undefined macro: AM_KDE_WITH_NLS
configure.in:320: error: possibly undefined macro: AC_PATH_KDE
I checked to see if I had gettext and I have gettext and gettext-devl 0.14.5-3. With a clean download of the cvs celestia, I got this:
Code: Select all
./configure --with-gnome --enable-lua=no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
./configure: line 1553: AM_INIT_AUTOMAKE: command not found
./configure: line 1554: syntax error near unexpected token `config.h'
./configure: line 1554: `AM_CONFIG_HEADER(config.h)'
Why was it compiling before and not now? Maybe I ran the wrong program first.
Posted: 22.09.2006, 04:47
by Brendan
I tried make -f Makefile.cvs, then ./configure --with-gnome --with-lua=no, then make and make install and still get the same gtk error.
Posted: 22.09.2006, 10:15
by phoenix
either your gtk-installation is broken or celestia can't find all the necessary gtk-libs.
I had a similar problem with my up-to-date gtk-installation when celestia compiled correct but when started it used some very old self-compiled gtk-libs in /usr/local/
Posted: 22.09.2006, 21:53
by Brendan
phoenix wrote:either your gtk-installation is broken or celestia can't find all the necessary gtk-libs.
I had a similar problem with my up-to-date gtk-installation when celestia compiled correct but when started it used some very old self-compiled gtk-libs in /usr/local/
I have gtk2-devel 2.8.20-1 installed and haven't compiled other versions.
Posted: 22.09.2006, 22:11
by phoenix
try running celestia with --dir and specify the directory of your celestia installation.
be sure that all files are readable and present.