autogen.sh was run without errors previously? 23.09.2009 01:04, Alexander Golec ?????: > Ok, so it turns out I had some trouble with my PATH. Now that that's > settled, here is the output of my ./configure: > > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... ./install-sh -c -d > checking for gawk... no > checking for mawk... no > checking for nawk... no > checking for awk... awk > checking whether make sets $(MAKE)... yes > checking whether ln -s works... yes > checking whether make sets $(MAKE)... (cached) 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 ISO C89... 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 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 a sed that does not truncate output... /usr/bin/sed > checking for Boost headers version>= 0... yes > checking for Boost's header version... ./configure: line 17699: syntax > error: unexpected end of file > > and sure enough, the file ends there, but not in any way foreign to > the syntax of the ./configure script. It's just a clean finish. > > On Sep 22, 10:32 am, Pahan-Hubbitus<[email protected]> wrote: > >> I think you should update your autoconf. You have 2.60 version but >> configuration was created in 2.64. >> >> 22.09.2009 00:50, Alexander Golec wrote: >> >> >> >> >>> So I tried to compile curlpp on Mac OS X Snow Leopard 10.6.1, and I >>> got this response from autogen.sh: >>> >>> $ ./autogen.sh >>> buildconf: autoconf version 2.60 (ok) >>> buildconf: autoheader version 2.60 (ok) >>> buildconf: automake version 1.10 (ok) >>> buildconf: libtool version 2.2.4 (ok) >>> buildconf: GNU m4 version 1.4.2 (ok) >>> buildconf: running libtoolize >>> buildconf: running aclocal >>> buildconf: running aclocal hack to convert all mv to mv -f >>> buildconf: running autoconf >>> aclocal.m4:17: error: this file was generated for autoconf 2.64. >>> You have another version of autoconf. If you want to use that, >>> you should regenerate the build system entirely. >>> aclocal.m4:17: the top level >>> autom4te-2.60: /sw/bin/gm4 failed with exit status: 63 >>> The command 'autoconf' failed >>> >>> This is after I tried building using my old autoconf 2.60, which >>> complained that I need 2.61. >>> >>> What gives? >>> > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "curlpp" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/curlpp?hl=en -~----------~----~----~----~------~----~------~--~---
