From: David Pirotte <david@altosw.be>
To: guile-gtk <guile-gtk@sourceware.cygnus.com>
Subject: gnome-guile, latest cvs, gnomeConf.sh not found
Date: Thu, 07 Feb 2002 13:45:00 -0000 [thread overview]
Message-ID: <3C62F524.9A0A1EE4@altosw.be> (raw)
Hello,
SuSE 7.3
guile-1.7.x (cvs download 4th fev 02)
gnome-1.4 is installed
but couldn't run autogen, here is the output. Where can I find gnomeConf.sh,
what module shoud it be part of?
thanks for some hint,
david
;; sh ./autogen.sh output
;; ----------------------------------------------------------------
david@faust:~/ftp/gnome/gnome-guile 134 $ sh ./autogen.sh
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`./autogen.sh' command line.
processing .
Running libtoolize...
You should update your `aclocal.m4' by running aclocal.
Running aclocal -I /usr/local/share/aclocal/gnome2-macros ...
Running autoheader...
autoheader: config.h.in is unchanged
Running automake --gnu ...
Running autoconf ...
configure.in:13: warning: AC_ARG_PROGRAM invoked multiple times
processing ./guile-gtk
Running libtoolize...
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `..'.
Running aclocal -I /usr/local/share/aclocal/gnome2-macros ...
aclocal: configure.in: 68: macro `AM_PATH_GTK' not found in library
Running autoheader...
autoheader: error: AC_CONFIG_HEADERS not found in configure.in
Running automake --gnu ...
configure.in: 3: required file `./config.h.in' not found
Makefile.am:42: variable `GTK_LIBS' not defined
Makefile.am:56: variable `GTK_LIBS' not defined
Makefile.am:67: variable `GUILE_LIBS' not defined
Running autoconf ...
configure.in:3: error: possibly undefined macro: AM_CONFIG_HEADER
configure.in:4: error: possibly undefined macro: AM_INIT_AUTOMAKE
configure.in:11: error: possibly undefined macro: AM_PROG_LIBTOOL
configure.in:26: error: possibly undefined macro: AM_PATH_GTK
processing ./guile-gtk/examples
Running libtoolize...
You should update your `aclocal.m4' by running aclocal.
Putting files in AC_CONFIG_AUX_DIR, `../..'.
Running aclocal -I /usr/local/share/aclocal/gnome2-macros ...
Running automake --gnu ...
Running autoconf ...
Running ./configure --enable-maintainer-mode --enable-compile-warnings ...
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for strerror in -lcposix... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking build system type... i686-suse-linux
checking host system type... i686-suse-linux
checking for ld used by GCC... /usr/i486-suse-linux/bin/ld
checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-suse-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/i486-suse-linux/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for gnome-config... no
checking for gnomeConf.sh file in /usr/local/lib... not found
configure: error: Could not find the gnomeConf.sh file that is generated by gnome-libs install
david@faust:~/ftp/gnome/gnome-guile 135 $
next reply other threads:[~2002-02-07 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 13:45 David Pirotte [this message]
2002-02-07 14:16 ` David Pirotte
2002-02-07 14:20 ` Neil W. Van Dyke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C62F524.9A0A1EE4@altosw.be \
--to=david@altosw.be \
--cc=guile-gtk@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).