[Muine] how to build cvs-muine?
- From: gabor <gabor z10n net>
- To: muine-list gnome org
- Subject: [Muine] how to build cvs-muine?
- Date: Mon, 07 Jun 2004 09:40:54 +0200
hi,
i once built muine from cvs, but now i reinstalled my laptop
(phew)...and...
what's the official way to build muine?
i checked it out from gnome-cvs, tried to run autogen.sh,
it complained that he cannot found gnome-common.
i checked out gnome-common from gnome-cvs, ./autogen.sh, make, make
install-to-a-special-dir, add special-dir to $PATH.
i started autogen.sh again, it went fine, then it started configure, and
it failed with:
appending configuration tag "F77" to libtool
./configure: line 19450: test: too many arguments
./configure: line 19493: GNOME_DEBUG_CHECK: command not found
./configure: line 19494: syntax error near unexpected token `error'
./configure: line 19494: `GNOME_COMPILE_WARNINGS(error)'
any ideas?
i attached the output of the autogen script, and you can find the
generated configure script (it was 700kb (150kb compressed), i didn't
want to send it to the list) at:
http://z10n.net/config-muine.gz
thanks,
gabor
/home/gabor/usr/bin/gnome-autogen.sh
[1mchecking for autoconf >= 2.53...
[m testing autoconf2.50... not found.
testing autoconf... found 2.59
[1mchecking for automake >= 1.7...
[m testing automake-1.7... found 1.7.9
[1mchecking for libtool >= 1.4.3...
[m testing libtoolize... found 1.5.2
[1mchecking for glib-gettext >= 2.2.0...
[m testing glib-gettextize... found 2.4.1
[1mchecking for intltool >= 0.25...
[m testing intltoolize... found 0.30
[1mchecking for pkg-config >= 0.14.0...
[m testing pkg-config... found 0.15.0
[1mChecking for required M4 macros...
[m[1mChecking for forbidden M4 macros...
[m**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.
[1mProcessing ./configure.in
[m[1mRunning libtoolize...
[m[1mRunning glib-gettextize... Ignore non-fatal messages.
[mCopying file po/Makefile.in.in
Please add the files
codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.
[1mRunning intltoolize...
[mpatching file po/Makefile.in.in
[1mRunning aclocal-1.7...
[m[1mRunning autoconf...
[m[1mRunning autoheader...
[m[1mRunning automake-1.7...
[m[1mRunning ./configure --enable-maintainer-mode ...
[mchecking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for intltool >= 0.21... 0.30 found
checking for perl... /usr/bin/perl
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for strerror in -lcposix... no
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for ld used by gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/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 dependent libraries... pass_all
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
./configure: line 19450: test: too many arguments
./configure: line 19493: GNOME_DEBUG_CHECK: command not found
./configure: line 19494: syntax error near unexpected token `error'
./configure: line 19494: `GNOME_COMPILE_WARNINGS(error)'
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]