Pavel,
Thanks for your prompt reply. I forgot the gcc-c++ package. However, after
installling that one I get another error when running make:
Last couple of lines from make
---------------------------------------------
rm -f .libs/utf8.lo
c++ -DHAVE_CONFIG_H -I. -I. -I../../autocfg -g -O2 -c utf8.cpp -fPIC -DPIC
-o .libs/utf8.lo
utf8.cpp: In function `int utf8Recode (char *, const char *,
Encoding)':
utf8.cpp:274: cannot convert `const char **' to `char **' for argument
`2' to `iconv (void *, char **, size_t *, char **, size_t *)'
make[2]: *** [utf8.lo] Error 1
make[2]: Leaving directory `/opt/usr/ton/xml/Sablot-0.50/Sablot/engine'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/opt/usr/ton/xml/Sablot-0.50/Sablot'
make: *** [all-recursive] Error 1
Make stops here
What to do?
Thanks again!
Ton
At 10:56 AM 2/7/01 +0100, you wrote:
>Ton,
>
>it doesn't look like a Sablotron problem, but GCC one.
>
>Strange thing is, that configure decides to use gcc as an c++ compiler
>(g++ would be much much better).
>
>The default compiler brought by RH 7.0 is OK, newer version shouldn't make
>anything wrong.
>
>Did you install gcc-c++ package?
>
>What about your CXX environment?
>
>Pavel
>
>Ton Verhagen wrote:
>
>>Dear All,
>>I encountered some problems with the installation of Sablotron 0.50.
>>According to the installation directions one would need gcc-2.95.2 or
>>higher. So I installed gcc-2.96-54-i386.rpm on a RedHat 7.0 system.
>>After issuing ./configure the configuration stops (see output at end of
>>this message)
>>Error message: C++ compiler cannot create executables
>>What could be wrong? Doesn't Sablotron support gcc-2.96?
>>Any help is much appreciated, as we would like to be using Sablotron soon.
>>Thanks a lot for your kind cooperation.
>>Ton Verhagen
>>
>>
>>Output from ./configure
>>------------------------------------------------------------------
>>creating cache ./config.cache
>>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... found
>>checking host system type... i686-pc-linux-gnu
>>checking build system type... i686-pc-linux-gnu
>>checking for ranlib... ranlib
>>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 ld used by GCC... /usr/bin/ld
>>checking if the linker (/usr/bin/ld) is GNU ld... yes
>>checking for BSD-compatible nm... /usr/bin/nm -B
>>checking whether ln -s works... yes
>>updating cache ./config.cache
>>checking for object suffix... o
>>checking for executable suffix... no
>>checking for gcc option to produce PIC... -fPIC
>>checking if gcc PIC flag -fPIC works... yes
>>checking if gcc supports -c -o file.o... yes
>>checking if gcc supports -c -o file.lo... yes
>>checking if gcc supports -fno-rtti -fno-exceptions ... yes
>>checking if gcc static flag -static works... -static
>>checking if the linker (/usr/bin/ld) is GNU ld... yes
>>checking whether the linker (/usr/bin/ld) supports shared libraries... yes
>>checking command to parse /usr/bin/nm -B output... ok
>>checking how to hardcode library paths into programs... immediate
>>checking for /usr/bin/ld option to reload object files... -r
>>checking dynamic linker characteristics... Linux ld.so
>>checking if libtool supports shared libraries... yes
>>checking whether to build shared libraries... yes
>>checking whether to build static libraries... yes
>>checking for objdir... .libs
>>creating libtool
>>loading cache ./config.cache
>>checking for gcc... (cached) gcc
>>checking whether the C compiler (gcc -g -O2 ) works... yes
>>checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
>>checking whether we are using GNU C... (cached) yes
>>checking whether gcc accepts -g... (cached) yes
>>checking how to run the C preprocessor... gcc -E
>>checking for c++... no
>>checking for g++... no
>>checking for gcc... gcc
>>checking whether the C++ compiler (gcc ) works... no
>>configure: error: installation or configuration problem: C++ compiler
>>cannot create executables.
>
>
>--
>Pavel Hlavnicka
>Ginger Alliance Ltd.
>Prague; Czech Republic
