#3 Suse RPM
I switched to Suse 9.3 from Fedora, and can't get gri
to install.
It is beyond me how to get this fixed. Is there a Suse
RPM anywhere?
Thanks
A.
aminer2k@yahoo.com
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 build system type... i686-suse-linux
checking host system type... i686-suse-linux
checking for ranlib... ranlib
checking for a BSD-compatible install...
/usr/bin/install -c
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 ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
checking for old C++ subroutine called string::remove... no
checking for gcc compiler... checking for egrep... grep -E
no
checking for C++ compiler with new headers as of August
2002... no
checking for DEC cxx compiler... no
checking for DEC alpha computer... no
checking for BeOS environment... no
checking for HPUX environment... no
checking for for Sun Microsystems computer... no
checking for for IBM AIX computer with IBM compiler... no
checking for for mingw32 system... no
checking to see whether this machine is big endian or
little endian... little
checking for ANSI C header files... no
checking for sys/types.h... no
checking for sys/stat.h... no
checking for stdlib.h... no
checking for string.h... no
checking for memory.h... no
checking for strings.h... no
checking for inttypes.h... no
checking for stdint.h... no
checking for unistd.h... no
checking for unistd.h... (cached) no
checking for netcdf library... no
checking for convert... yes
checking for ANSI C header files... (cached) no
checking for poptReadConfigFile in -lpopt... no
checking for pid_t... no
checking for isnan... no
checking for isinf... no
checking for acosh... no
checking for getcwd... no
checking for popen... no
checking for mkstemp... no
checking for tmpnam... no
checking for tempnam... no
checking for gethostname... no
checking for access... no
checking for lstat... no
checking for stat... no
checking for strerror... no
checking whether getenv is declared... no
checking whether drand48 is declared... no
configure: creating ./config.status
config.status: creating Makefile
config.status: creating debian/Makefile
config.status: creating doc/Makefile
config.status: creating doc/examples/Makefile
config.status: creating doc/tst_suite/Makefile
config.status: creating doc/resources/Makefile
config.status: creating doc/screenshots/Makefile
config.status: creating src/Makefile
config.status: creating src/popt/Makefile
config.status: executing depfiles commands
Logged In: YES
user_id=31559
Sorry, I can't really help. One thing that's odd is that it says it has 'gcc', but not
either 'g++' or 'c++'. That seems strange. You certainly need a c++ compiler
to build gri.
I'm sorry I didn't see this question for quite a while; it was not assigned to
anyone, so I got no notification when you submitted your note.
Dan.