dctc-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dctc-general] Problems compiling dctc-0.85.9


From: Joshue Martin
Subject: [Dctc-general] Problems compiling dctc-0.85.9
Date: Tue, 27 Jan 2004 13:28:02 +0100

        Hello.

I use a Slackware 8.1 version with libgcrypt installed. When I try to compile with:

/autogen.sh --prefix=/usr/local/dctc

processing .
Running libtoolize...
You should update your `aclocal.m4' by running aclocal.
Running aclocal  ...
Running autoheader...
configure.in:5: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
configure.in:348: warning: do not use m4_regexp: use regexp or m4_bregexp
autoheader: `config.h.in' is unchanged
Running automake --gnu  ...
Running autoconf ...
Running ./configure --enable-maintainer-mode --prefix=/usr/local/dctc ...
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking whether build environment is sane... yes
checking for style of include used by make... GNU
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 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 dependency style of gcc... gcc
checking for strerror in -lcposix... no
checking for gawk... (cached) gawk
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking dependency style of gcc... (cached) gcc
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/i386-slackware-linux/bin/ld
checking if the linker (/usr/i386-slackware-linux/bin/ld) is GNU ld... yes
checking for /usr/i386-slackware-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 how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
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 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/i386-slackware-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 gcc option to accept ANSI C... none needed
checking whether make sets ${MAKE}... (cached) yes
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking GCC version... 2.95.3
checking for libgcrypt-config... yes
checking gcrypt version... 1.1.91
./configure: line 8560: syntax error near unexpected token `PKG_CHECK_MODULES(GLIB,'
./configure: line 8560: `       PKG_CHECK_MODULES(GLIB, glib-2.0 gthread-2.0)'

        What can I do?

        Thanks.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]