[Varnish] #569: Cannot compile new trunk

Thu Oct 22 17:26:53 CEST 2009

#569: Cannot compile new trunk
-------------------+--------------------------------------------------------
 Reporter:  hp197  |        Type:  defect
   Status:  new    |    Priority:  normal
Milestone:         |   Component:  build 
  Version:  trunk  |    Severity:  normal
 Keywords:         |  
-------------------+--------------------------------------------------------
 I am having problems compiling the new trunk (Revision: 4337).

 {{{
 Checked out revision 4337.
 + aclocal
 + libtoolize --copy --force
 + autoheader
 + automake --add-missing --copy --foreign
 + autoconf
 + aclocal
 + libtoolize --copy --force
 + autoheader
 + automake --add-missing --copy --foreign
 + autoconf
 checking build system type... x86_64-redhat-linux-gnu
 checking host system type... x86_64-redhat-linux-gnu
 checking target system type... x86_64-redhat-linux-gnu
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for gawk... gawk
 checking whether make sets $(MAKE)... yes
 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 how to run the C preprocessor... gcc -E
 checking for a BSD-compatible install... /usr/bin/install -c
 checking for a sed that does not truncate output... /bin/sed
 checking for egrep... grep -E
 checking for ld used by gcc... /usr/bin/ld
 checking if the linker (/usr/bin/ld) is GNU ld... yes
 checking for /usr/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 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 g++... g++
 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 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 static flag -static works... yes
 checking if gcc supports -c -o file.o... yes
 checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) 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/bin/ld -m elf_x86_64
 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
 checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
 shared libraries... yes
 checking for g++ option to produce PIC... -fPIC
 checking if g++ PIC flag -fPIC works... yes
 checking if g++ static flag -static works... yes
 checking if g++ supports -c -o file.o... yes
 checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
 shared libraries... yes
 checking dynamic linker characteristics... GNU/Linux ld.so
 checking how to hardcode library paths into programs... immediate
 appending configuration tag "F77" to libtool
 checking whether make sets $(MAKE)... (cached) yes
 checking for xsltproc... no
 configure: WARNING: xsltproc not found â€“ not building documentation
 checking for clock_gettime in -lrt... yes
 checking for dlopen in -ldl... yes
 checking for library containing initscr... -lcurses
 checking for library containing pthread_create... -lpthread
 checking for socket in -lsocket... no
 checking for getaddrinfo in -lnsl... yes
 checking for cos in -lm... yes
 ./configure: line 19675: PKG_PROG_PKG_CONFIG: command not found
 ./configure: line 19677: syntax error near unexpected token `PCRE,'
 ./configure: line 19677: `   PKG_CHECK_MODULES(PCRE, libpcre)'
 }}}

 {{{
 # rpm -qf /usr/lib/pkgconfig/libpcre.pc
 pcre-devel-6.6-2.el5_1.7
 }}}

 {{{
 CentOS release 5.4 (Final)
 Linux 2.6.18-128.el5 #1 SMP Wed Jan 21 10:41:14 EST 2009 x86_64 x86_64
 x86_64 GNU/Linux
 }}}

 Did install all the latest packages from CentOS.
 I guess the problem is that my pkg-config is too old.

 Are you prepared to fix this or do i need to find a workaround for this
 one?

-- 
Ticket URL: <http://varnish.projects.linpro.no/ticket/569>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator