SCTP Discussions

Text archives Help


Re[4]: [SCTP-Discussion] Compilation problem


Chronological Thread 
  • From: Pawel Hadam <Pawel.Hadam AT imag.fr>
  • To: Andreas Jungmaier <ajung AT exp-math.uni-essen.de>
  • Cc: discussion AT sctp.de, "Elangovan, Sumathi " <Sumathi.Elangovan AT thalesgroup.com>
  • Subject: Re[4]: [SCTP-Discussion] Compilation problem
  • Date: Thu Apr 3 16:02:01 2003
  • List-id: SCTP Discussions <discussion.sctp.de>
  • Organization: LSR-IMAG

Hi Andreas,

AJ> you untar socket-api library into a directory, change into
AJ> that directory and *should* find an executable script named
AJ> "configure". If you don't, then please complain to the list,
AJ> and state that you grabbed a release that was not ready for
AJ> release.

Yes, I have found. It is OK.

AJ> Anyway, executing the "./configure" procedure should generate
AJ> some output (there should not be the need to call automake and
AJ> the like...we do that prior to making releases).

Yes. I did only ./configure and then make:

AJ> If you have problems at this stage, then post the output of
AJ> "configure".

Voila, here it goes:

sctp/socketapi-1.0.1# pwd
/home/root/install/sctp/socketapi-1.0.1

sctp/socketapi-1.0.1# ./configure
creating cache ./config.cache
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for c++... no
checking for g++... no
checking for gcc... gcc
checking whether the C++ compiler (gcc ) works... yes
checking whether the C++ compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether gcc accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ranlib... ranlib
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for ld used by GCC... /usr/i486-suse-linux/bin/ld
checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-suse-linux/bin/ld option to reload object files...
-r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependant libraries... pass_all
checking for object suffix... o
checking for executable suffix... no
checking for ranlib... (cached) ranlib
checking for strip... strip
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
finding the maximum length of command line arguments... 73729
checking if gcc supports -c -o file.o... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/i486-suse-linux/bin/ld) supports shared
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for dlopen in -ldl... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
updating cache ./config.cache
loading cache ./config.cache
checking for working const... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking size of char... 1
checking size of short... 2
checking size of int... 4
checking size of long... 4
checking size of long long... 8
checking for type socklen_t... yes
checking for glib-config... /usr/bin/glib-config
checking for GLIB - version >= 1.2.8... yes
checking checking whether sctplib/socketapi version are compatible...
********** sctplib/socketapi version checker **********
Current sctplib version: 0.19
Required sctplib version: 0.19
*******************************************************
compatible
updating cache ./config.cache
creating ./config.status
creating Makefile
creating socketapi/Makefile
creating cppsocketapi/Makefile
creating socket_programs/Makefile
creating cppsocket_programs/Makefile
creating config.h

sctp/socketapi-1.0.1# make
make all-recursive
make[1]: Entering directory `/home/root/install/sctp/socketapi-1.0.1'
Making all in socketapi
make[2]: Entering directory
`/home/root/install/sctp/socketapi-1.0.1/socketapi'
/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..
-I/usr/local/include -g -O2 -D_REENTRANT -D_THREAD_SAFE -Wall -DLINUX
-I/usr/local/include -c thread.cc
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include -g -O2 -D_REENTRANT
-D_THREAD_SAFE -Wall -DLINUX -I/usr/local/include -Wp,-MD,.deps/thread.pp
-c thread.cc -o thread.o
In file included from thread.cc:36:
tdsystem.h:80: iostream: No such file or directory
In file included from thread.h:40,
from thread.cc:37:
synchronizable.h:44: set: No such file or directory
In file included from thread.cc:37:
thread.h:45: set: No such file or directory
make[2]: *** [thread.lo] Error 1
make[2]: Leaving directory
`/home/root/install/sctp/socketapi-1.0.1/socketapi'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/root/install/sctp/socketapi-1.0.1'
make: *** [all-recursive-am] Error 2
sctp/socketapi-1.0.1#


AJ> Pawel, in your last mail, you posted that you started the make
AJ> process, so I suppose that the initial "./configure" went okay.

As you may see above.

AJ> The compilation barked out on you at line 80 in tdsystem.h
AJ> and line 45 in thread.h - so it might be useful to have a look
AJ> in these files.
AJ> tdsystem.h:80: #include <iostream>
AJ> thread.h:45: #include <set>

AJ> I think, this could mean that you might not have a proper
AJ> libstdc++ installed on your system.

My /usr/lib contains:

-rw-r--r-- 1 root root 494296 Apr 12 2002
libg++-3-libc6.2-2-2.8.1.3.a
-r-xr-xr-x 1 root root 365795 Apr 12 2002
libg++-3-libc6.2-2-2.8.1.3.so
lrwxrwxrwx 1 root root 28 Mar 7 16:18
libg++-libc6.2-2.a.3 -> libg++-3-libc6.2-2-2.8.1.3.a
lrwxrwxrwx 1 root root 29 Mar 7 16:18
libg++-libc6.2-2.so.3 -> libg++-3-libc6.2-2-2.8.1.3.so
-rwxr-xr-x 1 root root 1227181 Apr 12 2002
libstdc++-3-libc6.1-2-2.10.0.so
-rw-r--r-- 1 root root 512336 Apr 12 2002
libstdc++-3-libc6.2-2-2.10.0.a
-r-xr-xr-x 1 root root 376154 Apr 12 2002
libstdc++-3-libc6.2-2-2.10.0.so
-rwxr-xr-x 1 root root 1225930 Apr 12 2002
libstdc++-libc6.1-1.so.2
lrwxrwxrwx 1 root root 31 Mar 7 16:20
libstdc++-libc6.1-2.so.3 -> libstdc++-3-libc6.1-2-2.10.0.so
lrwxrwxrwx 1 root root 30 Mar 7 16:18
libstdc++-libc6.2-2.a.3 -> libstdc++-3-libc6.2-2-2.10.0.a
lrwxrwxrwx 1 root root 31 Mar 7 16:18
libstdc++-libc6.2-2.so.3 -> libstdc++-3-libc6.2-2-2.10.0.so


And:


/usr/lib# ls -al | grep glib
drwxr-xr-x 3 root root 4096 Apr 2 15:48 glib
lrwxrwxrwx 1 root root 21 Mar 7 16:26 libglib-1.2.so.0
-> libglib-1.2.so.0.0.10
-rwxr-xr-x 1 root root 169165 Apr 12 2002
libglib-1.2.so.0.0.10
-rw-r--r-- 1 root root 200356 Apr 12 2002 libglib.a
-rwxr-xr-x 1 root root 662 Apr 12 2002 libglib.la
lrwxr-xr-x 1 root root 21 Apr 2 15:48 libglib.so ->
libglib-1.2.so.0.0.10
/usr/lib#



All that I did under 2.4.18. I did not tested with 2.4.17.
With 2.5.65 I met also some other problem, I had to replace line 1162 in
./configure line:

ac_ext=C

by

ac_ext=c

After this change ./configure went OK, but make gave the same error as
shown above.

I hope this will help you to solve this problem.
Regards
Pawel






Archive powered by MHonArc 2.6.19+.

Top of page