[prev in list] [next in list] [prev in thread] [next in thread] 

List:       stunnel-users
Subject:    Compiling stunnel 3.22 on Irix 6.5.14: "common.h:134: parse error"
From:       Andy Ozment <andy.ozment () cc ! gatech ! edu>
Date:       2002-07-12 16:07:33
[Download RAW message or body]

Hi,

Here are the stats:
Irix 6.5.14 (6.5 10100655 IP22)
stunnel 3.22
gcc 2.95.2
openssl 0.9.6b

configure options I'm using:
CC=/usr/local/bin/gcc-2.95.2 
LDFLAGS=-L/usr/local/lib 
./configure
--prefix=/usr
--with-egd-socket=/var/run/egd-pool
--with-pem-dir=/etc/ssl/certs
--with-cert-dir=/etc/ssl/certs
--with-cert-file=/etc/ssl/certs/ca-bundle.crt
--with-tcp-wrappers

The LDFLAGS option is to indicate the directory where the tcp wrappers
library is stored. I got the error below regardless of whether or not I
included the LDFLAGS option.

Unfortunately, when I try to compile, it chokes:


        /usr/local/bin/gcc-2.95.2 -g -O2 -Wall -I/usr/include
-I/usr/local/include -DVERSION=\"3.22\" -DHAVE_OPENSSL=1
-Dssldir=\"/usr\" -DPEM_DIR=\"/etc/ssl/certs\"
-DPEM_DIR=\"/etc/ssl/certs\"
-DCERT_FILE=\"/etc/ssl/certs/ca-bundle.crt\"
-DCERT_DIR=\"/etc/ssl/certs\" -DEGD_SOCKET=\"/var/run/egd-pool\"
-DNO_DH=1 -DHOST=\"mips-sgi-irix6.5\" -DHAVE_LIBDL=1 -DHAVE_LIBNSL=1
-DHAVE_LIBSOCKET=1 -DHAVE_LIBPTHREAD=1 -DHAVE_LIBWRAP=1
-DHAVE_DEV_PTMX=1 -DHAVE_DEV_PTS_AND_PTC=1 -DHAVE_GETOPT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_TCPD_H=1
-DHAVE_PTHREAD_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_STROPTS_H=1
-DHAVE_SYS_FILIO_H=1 -DHAVE_SYS_RESOURCE_H=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_UNISTD_H=1 -DSIZEOF_UNSIGNED_CHAR= -DSIZEOF_UNSIGNED_SHORT=
-DSIZEOF_UNSIGNED_INT= -DSIZEOF_UNSIGNED_LONG=
-DSIZEOF_UNSIGNED_LONG_LONG=  -Dlibdir=\"/usr/lib\"
-DPIDDIR=\"/var/run\" -c client.c
In file included from client.c:37:
common.h:134: parse error
common.h:138: parse error
common.h:144: parse error
common.h:150: parse error


A previous post suggested that this error was due to a problem with the
configure.ac script which would be fixed in the next release. It went on
to state that the solution was to add the --with-tcp-wrappers option to
the configure script. As you can see, I've done that, but I am still
encountering the problem.

Any other suggestions?

Thank you!
Andy
[prev in list] [next in list] [prev in thread] [next in thread]