gnome-libs autogen bug
- From: Todd Graham Lewis <tlewis mindspring net>
- To: gnome nuclecu unam mx
- Subject: gnome-libs autogen bug
- Date: Wed, 15 Jul 1998 19:09:35 -0400 (EDT)
checking for GTK - version >= 1.0.1... ./configure: /usr/bin/gtk-config: No such file or directory
./configure: /usr/bin/gtk-config: No such file or directory
./configure: /usr/bin/gtk-config: No such file or directory
./configure: /usr/bin/gtk-config: No such file or directory
./configure: /usr/bin/gtk-config: No such file or directory
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 gtk-config script: /usr/bin/gtk-config
configure: error: GTK not installed
reflections# /home/tlewis/gnome/cvs/gnome-libs
Of course, gtk-config lives in /usr/local/bin. If autogen had either
an obvious way to specify a prefix of /usr/local, or a --help option
which revealed a non-obvious way, or if it attempted to run gtk-config
with an unqialified pathname, since putting /usr/local in my path is an
obvious thing which I can do without delving into autoconf &al.
For now, I'm just symlinking gtk-config into /usr/bin, since my goal is
to get a build done, but I don't like it. Hey, this might be a good
opportunity for me to understand the bug-tracking system and add a
section on that, too!
--
Todd Graham Lewis (800) 719-4664, x2804
******Linux****** MindSpring Enterprises tlewis@mindspring.net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]