Roland0 wrote: > In buildme.sh, try replacing > > Code: -------------------- > > > DBI) > if [ "$PERL_518" -o "$PERL_520" ]; then > build_module DBI-1.628 > else > build_module DBI-1.616 > fi > ;; > -------------------- > > > with > > Code: -------------------- > > > DBI) > RUN_TESTS=0 > if [ "$PERL_518" -o "$PERL_520" ]; then > build_module DBI-1.628 > else > build_module DBI-1.616 > fi > RUN_TESTS=1 > ;; > -------------------- > >
Alright... hacking out the tests stopped the DBI build from failing. ;-D Although... the test failures looked pretty fundamental. If the tests don't pass is this thing going to run once it is built? Anyway, next problem is the ICU module... that's now failing with export CPP= CC=gcc CXX=g++ CPPFLAGS= CFLAGS=-fPIC -DU_USING_ICU_NAMESPACE=0 -O3 CXXFLAGS=-fPIC -DU_USING_ICU_NAMESPACE=0 -O3 LDFLAGS=-fPIC MAKE=/usr/bin/make Running ./configure --prefix=/home/rich/LMS-SelfContained/7.7-CPAN/slimserver-vendor-public-7.7/CPAN/build --enable-static --with-data-packaging=archive for Linux using the GNU C++ compiler checking for ICU version numbers... release 4.6, library 46.0, unicode version 6.0 checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking whether to build debug libraries... no checking whether to build release libraries... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no 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 ISO C89... none needed checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /bin/install -c checking for gmake... /bin/gmake checking for doxygen... no checking checking for executable suffix... checking whether strict compiling is on... yes checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E 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 size of void *... 8 checking whether runnable 64 bit binaries are built by default... yes checking which Makefile fragment to use for x86_64-unknown-linux-gnu... mh-linux checking for floor in -lm... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether to enable auto cleanup of libraries... no checking whether to enable draft APIs... yes checking for library API export... yes checking for ranlib... ranlib checking for ar... ar checking whether to enable renaming of symbols... yes checking whether to enable function and data tracing... no checking whether to enable dynamic loading of plugins... checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for library containing dlopen... -ldl checking for dlopen... yes checking for gettimeofday... yes checking for definition of U_INLINE for C... __inline__ checking if we have a C++ compiler... no configure: error: C++ compiler g++ does not work or no compiler found ./runConfigureICU: ./configure failed make: *** No targets specified and no makefile found. Stop. make failed Not sure why it fails saying their is no C++ compiler when at the top it said it was using Gnu... But these build errors are making me wonder if their is something more fundamental wrong. Is it usually this... fragile? Rich ------------------------------------------------------------------------ Stanbey's Profile: http://forums.slimdevices.com/member.php?userid=64525 View this thread: http://forums.slimdevices.com/showthread.php?t=99648
_______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix