qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Huston" <shus...@riverace.com>
Subject RE: autoconf issue? (was Re: send/receive to/from remote machine)
Date Wed, 25 Mar 2009 15:03:13 GMT
> ft420 wrote:
> > Hi Gordon,
> > 
> > I hope you checked the flow of what happens when 
> ./configure is done... 
> > If possible please let me know solution for the same... 
> 
> It has me stumped at present I'm afraid. It looks to me like its an 
> issue with autoconf but I couldn't swear to it. Any experts 
> on the list able to comment?

Expert, I am not. But can you please look at your configure file line
19936 and see if there really is &amp; there? It should be simply &&

-Steve

> > ./bootstrap works properly but ./configure gives problem. 
> Please find below whatever is displayed when i execute ./configure 
> > 
> > [root@FTCPU1452 cpp]# ./configure
> > 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 style of include used by make... GNU
> > 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 dependency style of gcc... gcc3
> > checking whether gcc and cc understand -c and -o together... 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... gcc -E
> > checking for egrep... grep -E
> > checking for AIX... no
> > 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 minix/config.h usability... no
> > checking minix/config.h presence... no
> > checking for minix/config.h... no
> > checking whether it is safe to define __EXTENSIONS__... yes
> > checking whether compiler accepts -Werror... yes
> > checking whether compiler accepts -pedantic... yes
> > checking whether compiler accepts -Wall... yes
> > checking whether compiler accepts -Wextra... yes
> > checking whether compiler accepts -Wno-shadow... yes
> > checking whether compiler accepts -Wpointer-arith... yes
> > checking whether compiler accepts -Wcast-qual... yes
> > checking whether compiler accepts -Wcast-align... yes
> > checking whether compiler accepts -Wno-long-long... yes
> > checking whether compiler accepts -Wvolatile-register-var... yes
> > checking whether compiler accepts -Winvalid-pch... yes
> > checking whether compiler accepts -Wno-system-headers... yes
> > checking build system type... i686-redhat-linux-gnu
> > checking host system type... i686-redhat-linux-gnu
> > checking for a sed that does not truncate output... /bin/sed
> > 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 dlfcn.h usability... yes
> > checking dlfcn.h presence... no
> > configure: WARNING: dlfcn.h: accepted by the compiler, 
> rejected by the preprocessor!
> > configure: WARNING: dlfcn.h: proceeding with the compiler's result
> > checking for dlfcn.h... yes
> > 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... f95
> > checking whether we are using the GNU Fortran 77 compiler... yes
> > checking whether f95 accepts -g... yes
> > 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) 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... no
> > configure: creating libtool
> > appending configuration tag "CXX" to libtool
> > checking for ld used by g++... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking whether the g++ linker (/usr/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++ static flag -static works... yes
> > checking if g++ supports -c -o file.o... yes
> > checking whether the g++ linker (/usr/bin/ld) 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 if libtool supports shared libraries... yes
> > checking whether to build shared libraries... yes
> > checking whether to build static libraries... no
> > checking for f95 option to produce PIC... -fPIC
> > checking if f95 PIC flag -fPIC works... yes
> > checking if f95 static flag -static works... yes
> > checking if f95 supports -c -o file.o... yes
> > checking whether the f95 linker (/usr/bin/ld) supports 
> shared libraries... yes
> > checking dynamic linker characteristics... GNU/Linux ld.so
> > checking how to hardcode library paths into programs... immediate
> > ./configure: line 19936: syntax error near unexpected token `&'
> > ./configure: line 19936: `  test $fail = 1 &amp;&amp;'
> > 
> > 
> > hopefully this will give you idea regarding where the problem
is....
> > 
> > Thanks
> > 
> > 
> > 
> 
> 
>
---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:users-subscribe@qpid.apache.org
> 


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org


Mime
View raw message