Re: Prelude-Correlator auto* command issues

Robin Gruyters <[email protected]>
Newsgroups gmane.comp.security.ids.prelude.devel
Message-ID <[email protected]>
ScottO,

Thanks for the info. I have just install autoconf-2.61 and automake-1.10_1
and looks like it is working.

Thanks anyway for the snapshot release link.

Regards,
-- 
Robin Gruyters
Network and Security Engineer
Yirdis B.V.
I: http://yirdis.com
P: +31 (0)36 5300394
F: +31 (0)36 5489119

On Wed, Apr 11, 2007 at 07:13:12AM -0400, ScottO wrote:
> Hi Robin,
> 
> I ran into a similar issue, the problem I was told, was an older version 
> of autoconf I had, I think I may have had the same version as you.
> 
> At any rate, I was directed to the snapshots section of the website: 
> http://www.prelude-ids.org/download/snapshots/trunk/
> 
> If you download the latest Correlator tarball from there, all you'll 
> need is a:  ./configure; make; make install
> 
> ScottO
> 
> Robin Gruyters wrote:
> >Hello,
> >
> >I have finally managed to find some time to test the new Prelude Correlator
> >tool.
> >Although I can't configure/install it.
> >
> >I have always issues when it comes to use automake/autoconf:
> >
> >[...]
> >$ autoreconf259 -i -f
> >aclocal:configure.in:8: warning: macro `AM_DISABLE_STATIC' not found in
> >library
> >configure.in:8: error: possibly undefined macro: AM_DISABLE_STATIC
> >      If this token and others are legitimate, please use m4_pattern_allow.
> >      See the Autoconf documentation.
> >configure.in:24: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
> >configure.in:25: error: possibly undefined macro: AC_PROG_LIBTOOL
> >configure.in:50: error: possibly undefined macro: AC_TYPE_SSIZE_T
> >configure:6572: error: possibly undefined macro: AC_PROG_MKDIR_P
> >autoreconf259: /usr/local/bin/autoconf259 failed with exit status: 1
> >$
> >[...]
> >
> >I have tried to run it manually:
> >[...]
> >$ cp /usr/local/share/aclocal/libtool.m4 aclocal.m4
> >$ libtoolize -f -c
> >$ aclocal19 -I /usr/local/share/aclocal
> >$ autoheader259 -f
> >$ automake19 -a -c
> >configure.in: installing `./install-sh'
> >configure.in: installing `./missing'
> >libmissing/Makefile.am: installing `./depcomp'
> >$ autoconf259 -f
> >configure.in:50: error: possibly undefined macro: AC_TYPE_SSIZE_T
> >      If this token and others are legitimate, please use m4_pattern_allow.
> >      See the Autoconf documentation.
> >$ ./configure --prefix=/usr/local
> >checking build system type... i386-unknown-freebsd6.1
> >checking host system type... i386-unknown-freebsd6.1
> >checking target system type... i386-unknown-freebsd6.1
> >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 whether to enable maintainer-specific portions of Makefiles... no
> >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 how to run the C preprocessor... gcc -E
> >checking for gcc... (cached) gcc
> >checking whether we are using the GNU C compiler... (cached) yes
> >checking whether gcc accepts -g... (cached) yes
> >checking for gcc option to accept ANSI C... (cached) none needed
> >checking dependency style of gcc... (cached) gcc3
> >gl_EARLY: not found
> >checking for a BSD-compatible install... /usr/bin/install -c
> >checking whether make sets $(MAKE)... (cached) yes
> >checking for inline... inline
> >checking whether byte ordering is bigendian... no
> >checking for a sed that does not truncate output... /usr/local/bin/gsed
> >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... f77
> >checking whether we are using the GNU Fortran 77 compiler... yes
> >checking whether f77 accepts -g... yes
> >checking the maximum length of command line arguments... 196608
> >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... yes
> >checking dynamic linker characteristics... freebsd6.1 ld.so
> >checking how to hardcode library paths into programs... immediate
> >checking whether stripping libraries is possible... yes
> >checking for shl_load... no
> >checking for shl_load in -ldld... no
> >checking for dlopen... yes
> >checking whether a program can dlopen itself... yes
> >checking whether a statically linked program can dlopen itself... no
> >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... freebsd6.1 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 f77 option to produce PIC... -fPIC
> >checking if f77 PIC flag -fPIC works... yes
> >checking if f77 static flag -static works... yes
> >checking if f77 supports -c -o file.o... yes
> >checking whether the f77 linker (/usr/bin/ld) supports shared libraries...
> >yes
> >checking dynamic linker characteristics... freebsd6.1 ld.so
> >checking how to hardcode library paths into programs... immediate
> >./configure.lineno: 19827: Syntax error: word unexpected (expecting ")")
> >$
> >[...]
> >
> >I'm running FreeBSD 6.1 and installed autoconf-2.59_2 and automake-1.9.6
> >packages.
> >
> >Regards,
_______________________________________________
Prelude-devel site list
[email protected]
http://www.prelude-ids.org/mailman/listinfo/prelude-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.