|
|
Blitz Support : |
From: Patrick Guio (patrick.guio_at_[hidden])
Date: 2003-06-23 03:54:44
On Mon, 23 Jun 2003, Mads Ipsen wrote:
Hi Mads,
Blit is now using libtool in addition to autoconf/automake in order to
build the library. So you should either run "libtoolize -c" in addition to
"aclocal; autoheader; automake -a; autoconf" in order to install the
libtool files like "ltmain.sh" or more simply just run "autoreconf -vif"
that will prepare every component of the configuration tools.
Sincerely,
Patrick
> Dear Julian,
>
> Some month ago I reported a bunch of errors and warnings that popped up
> when you compiled blitz dependent sources with gcc and the warning flags:
> '-Wall -W'. As you already responded, fixes for this were added to the
> CVS snapshot. I can't, however, seem to compile this. I've added some
> (hopefully) relevant output below
>
> Best, Mads
>
> aclocal; autoheader; automake -a; autoconf
>
> gives:
>
> autoheader: error: AC_CONFIG_HEADERS not found in configure.in
> configure.in: installing `./install-sh'
> configure.in: installing `./mkinstalldirs'
> configure.in: installing `./missing'
> configure.in:5: installing `./config.guess'
> configure.in:5: installing `./config.sub'
> configure.in:399: required file `./ltmain.sh' not found
> benchmarks/Makefile.am: installing `./depcomp'
>
> and afterwards, just typing make gives
>
> Making all in bin
> make[1]: Entering directory `/home/mpi/blitz/bin'
> make[1]: Nothing to be done for `all'.
> make[1]: Leaving directory `/home/mpi/blitz/bin'
> Making all in compiler
> make[1]: Entering directory `/home/mpi/blitz/compiler'
> ./bzconfig --compiler=g++ --flags="" --srcdir=.
>
> Blitz++ compiler evaluation
>
> This script will test your compiler to determine which language
> features it supports.
>
>
> I am now going to try a simple program.
> Okay, it compiled. But will it link?
> Yes, it linked too. Great.
>
>
> Okay, now the fun begins.
>
>
> Does your compiler implement namespaces?
> Yes.
>
> What about exceptions?
> Yes.
>
> Run-Time Type Identification?
> Yes.
>
> Member constants?
> Yes.
>
> Does your compiler cling to the old 'for' scoping rules?
> Nope.
>
> Now for some of the new keywords.
>
> How about the 'explicit' keyword?
> Yes.
>
> What about the 'mutable' keyword?
> Yes.
>
> Does your compiler recognize 'typename'?
> Yes.
>
> Just on the off chance... the NCEG 'restrict' keyword?
> Nope.
>
> Maybe it recognizes __restrict__?
> Yes.
>
> Does it recognize bool as a built-in type?
> Yes.
>
> Does your compiler understand the newfangled casting syntax?
>
> What about const_cast<>?
> Yes.
>
> static_cast<>?
> Yes.
>
> reinterpret_cast<>?
> Yes.
>
> dynamic_cast<>?
> Yes.
>
> Okay, now the important stuff -- templates.
>
> Will it handle basic templates? (If not, just give up now.)
> Yes.
>
> Partial specialization?
> Yes.
>
> Partial ordering?
> Yes.
>
> Default template parameters?
> Yes.
>
> Member templates?
> Yes.
>
> Member templates outside the class declaration?
> Yes.
>
> Does it recognize the full specialization syntax?
> Yes.
>
> Function templates with non-type parameters?
> Yes.
>
> Template-qualified base class specifiers?
> Yes.
>
> Template-qualified return types (necessary for vector type promotion)?
> Yes.
>
> Explicit template function qualification?
> Yes.
>
> Templates as template arguments?
> Yes.
>
> Use of the template keyword as a qualifier?
> Yes.
>
> Function matching with argument types which are template scope-qualified?
> Yes.
>
> Will it support the vector type promotion mechanism?
> Yes.
>
> Numeric traits promotions (sum type, etc.)?
> Yes.
>
> Can your compiler handle computations inside an enum?
> Yes.
>
> Does it handle (int) casts in enum computations?
> Yes.
>
> Which library features does your compiler provide?
>
> Does it have complex<T>?
> Yes.
>
> Does it have numeric_limits<T>?
> Yes.
>
> Does it have <climits>?
> Yes.
>
> Does it have valarray<T>?
> Yes.
>
> Complex math functions?
> Yes.
>
> IEEE Math library?
> Yes.
>
> System V Math library?
> Nope.
>
> Are C math functions in <cmath> and std::?
> Yes.
>
> Are complex math functions in std::?
> Yes.
>
> ISO C++ Standard library?
> Yes.
>
> Standard template library?
> Yes.
>
> What about getrusage()?
> Yes.
>
> The results have been written to the file config.h.
> If you're curious about which tests passed and failed and why, see
> this file:
> -rw-r--r-- 1 mpi users 5451 2003-06-23 10:39 logfile
> cp config.h ../blitz/config.h
> make[1]: Leaving directory `/home/mpi/blitz/compiler'
> Making all in blitz
> make[1]: Entering directory `/home/mpi/blitz/blitz'
> Making all in generate
> make[2]: Entering directory `/home/mpi/blitz/blitz/generate'
> if g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"Blitz++\"
> -DVERSION=\"0.6\" -DSTDC_HEADERS=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_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1
> -DHAVE_LIBM=1 -I. -I.
> -MT genarrbops.o -MD -MP -MF ".deps/genarrbops.Tpo" \
> -c -o genarrbops.o `test -f 'genarrbops.cpp' || echo
> './'`genarrbops.cpp; \
> then mv ".deps/genarrbops.Tpo" ".deps/genarrbops.Po"; \
> else rm -f ".deps/genarrbops.Tpo"; exit 1; \
> fi
> /bin/sh ../../libtool --mode=link g++ -o genarrbops genarrbops.o -lm
> ../../libtool: ../../libtool: No such file or directory
> make[2]: *** [genarrbops] Error 127
> make[2]: Leaving directory `/home/mpi/blitz/blitz/generate'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/mpi/blitz/blitz'
> make: *** [all-recursive] Error 1
> fred:blitz(801)>
>
>
> _______________________________________________
> Blitz-support mailing list
> Blitz-support_at_[hidden]
> http://www.oonumerics.org/mailman/listinfo.cgi/blitz-support
>
======================================================================
Patrick Guio
Institute of Physics, University of Oslo
P.O. box 1048, Blindern, N-0316 Oslo
Tel : (+47) 22 84 40 60 - Fax : (+47) 22 85 56 71
E-mail : patrick.guio_at_[hidden]
URL : http://folk.uio.no/~patricg