Hello, I tried to investigate the problem a little bit deeper. The problem seems to be hidden in the configure script and I have no idea how to fix that. This is from a build which I tried at crest.debian.org in an unstable chroot
> .... > checking for pkg-config... /usr/bin/pkg-config > checking for GTK+ - version >= 2.0.0... no > *** Could not run GTK+ test program, checking why... > *** The test program failed to compile or link. See the file config.log for > the > *** exact error that occured. This usually means GTK+ was incorrectly > installed > *** or that you have moved GTK+ since it was installed. In the latter case, > you > *** may want to edit the pkg-config script: /usr/bin/pkg-config > configure: creating ./config.status I just stopped here because this should not happen. File config.log says: > .... > > configure:7454: result: /usr/bin/pkg-config > configure:7474: checking for GTK+ - version >= 2.0.0 > configure:7586: gcc -o conftest -g -O2 -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include - > I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 > -I/usr/include/gli > b-2.0 -I/usr/lib/glib-2.0/include conftest.c -Wl,--export-dynamic > -lgtk-x11-2.0 -lgdk- > x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 > -lpango-1.0 -lgobject-2 > ..0 -lgmodule-2.0 -ldl -lglib-2.0 >&5 > /usr/lib/gcc-lib/m68k-linux/3.2.3/../../../libgdk-x11-2.0.so: undefined > reference to `Xine > ramaIsActive' > /usr/lib/gcc-lib/m68k-linux/3.2.3/../../../libgdk-x11-2.0.so: undefined > reference to `Xine > ramaQueryScreens' > collect2: ld returned 1 exit status > configure:7589: $? = 1 > configure: program exited with status 1 > configure: failed program was: > #line 7510 "configure" > .... I have really no idea what to do and I hope somebody could help me out here. Kind regards Andreas. -- The good thing about standards is that there are so many to choose from. -- Andrew S. Tanenbaum