Yes, in /home/kjetil/sage/sage-5.8/local/lib there are the following (among others):
libblas libcblas libatlas (.*) ¿Why are they not picked up? Kjetil On Thu, Apr 4, 2013 at 10:52 PM, François Bissey <francois.bis...@canterbury.ac.nz> wrote: > On Thu, 04 Apr 2013 18:56:33 Kjetil brinchmann Halvorsen wrote: >> OS version information: >> >> kjetil@kjetil-HP-Pavilion-dv4-Notebook-PC:~$ lsb_release >> LSB Version: >> core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64 >> :core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noar >> ch kjetil@kjetil-HP-Pavilion-dv4-Notebook-PC:~$ gcc --version >> gcc (Ubuntu/Linaro 4.7.2-2ubuntu1) 4.7.2 >> Copyright (C) 2012 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >> >> And, I DO have blas installed, the following ubuntu packages: >> libblas-dev AND libopenblas-dev, at the latests versions. >> >> Output from make: >> >> checking for other BLAS... problem >> Sorry, your BLAS are not working. Disabling. >> >> **************************************************************************** >> *** ERROR: BLAS not found! >> >> BLAS routines are required for this library to compile. Please >> make sure BLAS are installed and specify its location with the option >> --with-blas=<lib> when running configure (or --with-cblas... see configure >> --help). >> **************************************************************************** >> *** Error configuring linbox >> >> real 0m19.886s >> user 0m9.377s >> sys 0m2.712s >> ************************************************************************ >> Error installing package fflas_ffpack-1.6.0.p0 >> ************************************************************************ >> Please email sage-devel (http://groups.google.com/group/sage-devel) >> explaining the problem and including the relevant part of the log file >> /home/kjetil/sage/sage-5.8/spkg/logs/fflas_ffpack-1.6.0.p0.log >> Describe your computer, operating system, etc. >> If you want to try to fix the problem yourself, *don't* just cd to >> /home/kjetil/sage/sage-5.8/spkg/build/fflas_ffpack-1.6.0.p0 and type 'make' >> or whatever is appropriate. >> Instead, the following commands setup all environment variables >> correctly and load a subshell for you to debug the error: >> (cd '/home/kjetil/sage/sage-5.8/spkg/build/fflas_ffpack-1.6.0.p0' && >> '/home/kjetil/sage/sage-5.8/sage' -sh) >> When you are done debugging, you can type "exit" to leave the subshell. >> ************************************************************************ >> make[2]: *** [installed/fflas_ffpack-1.6.0.p0] Error 1 >> make[2]: Leaving directory `/home/kjetil/sage/sage-5.8/spkg' >> make[1]: *** [all] Error 2 >> make[1]: Leaving directory `/home/kjetil/sage/sage-5.8/spkg' >> >> real 0m20.656s >> user 0m9.833s >> sys 0m2.800s >> Error building Sage. >> make: *** [build] Error 1 >> >> Files asked about above: >> >> Thread model: posix >> gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) >> **************************************************** >> patching file fflas-ffpack-config.in >> Linux cblas >> ************************************************* >> Using LINBOX_BLAS=-lcblas -latlas >> ************************************************* >> checking for a BSD-compatible install... /usr/bin/install -c >> checking whether build environment is sane... yes >> checking for a thread-safe mkdir -p... /bin/mkdir -p >> checking for gawk... gawk >> checking whether make sets $(MAKE)... yes >> checking for rm... /bin/rm >> checking whether to enable maintainer-specific portions of Makefiles... no >> ----------------------------------------------- >> checking whether to enable debugging options in the library... no >> checking whether to enable profiling everything in the library... no >> checking whether to enable warnings when compiling the library... no >> ----------------------------------------------- >> 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 g++ accepts -g... yes >> checking for family name of compiler... gcc >> checking how to run the C++ preprocessor... g++ -E >> 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 build system type... x86_64-unknown-linux-gnu >> checking host system type... x86_64-unknown-linux-gnu >> checking how to print strings... printf >> checking for gcc... gcc >> 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 for a sed that does not truncate output... /bin/sed >> checking for fgrep... /bin/grep -F >> checking for ld used by gcc... ld >> checking if the linker (ld) is GNU ld... yes >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >> checking the name lister (/usr/bin/nm -B) interface... BSD nm >> checking whether ln -s works... yes >> checking the maximum length of command line arguments... 3458764513820540925 >> checking whether the shell understands some XSI constructs... yes >> checking whether the shell understands "+="... yes >> checking how to convert x86_64-unknown-linux-gnu file names to >> x86_64-unknown-linux-gnu format... func_convert_file_noop >> checking how to convert x86_64-unknown-linux-gnu file names to toolchain >> format... func_convert_file_noop >> checking for ld option to reload object files... -r >> checking for objdump... objdump >> checking how to recognize dependent libraries... pass_all >> checking for dlltool... no >> checking how to associate runtime and link libraries... printf %s\n >> checking for archiver @FILE support... @ >> checking for strip... strip >> checking for ranlib... ranlib >> checking command to parse /usr/bin/nm -B output from gcc object... ok >> checking for sysroot... no >> checking for mt... mt >> checking if mt is a manifest tool... no >> 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 for dlfcn.h... yes >> checking for objdir... .libs >> checking if gcc supports -fno-rtti -fno-exceptions... no >> 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 >> checking if gcc supports -c -o file.o... yes >> checking if gcc supports -c -o file.o... (cached) yes >> checking whether the gcc linker (ld -m elf_x86_64) supports shared >> libraries... yes >> checking whether -lc should be explicitly linked in... no >> checking dynamic linker characteristics... GNU/Linux ld.so >> checking how to hardcode library paths into programs... immediate >> checking whether stripping libraries is possible... yes >> checking if libtool supports shared libraries... yes >> checking whether to build shared libraries... yes >> checking whether to build static libraries... no >> checking how to run the C++ preprocessor... g++ -E >> checking for ld used by g++... ld -m elf_x86_64 >> checking if the linker (ld -m elf_x86_64) is GNU ld... yes >> checking whether the g++ linker (ld -m elf_x86_64) supports shared >> libraries... yes >> checking for g++ option to produce PIC... -fPIC -DPIC >> checking if g++ PIC flag -fPIC -DPIC works... yes >> checking if g++ static flag -static works... yes >> checking if g++ supports -c -o file.o... yes >> checking if g++ supports -c -o file.o... (cached) yes >> checking whether the g++ linker (ld -m elf_x86_64) supports shared >> libraries... yes >> checking dynamic linker characteristics... (cached) GNU/Linux ld.so >> checking how to hardcode library paths into programs... immediate >> ----------------------------------------------- >> checking size of char... 1 >> checking size of short... 2 >> checking size of int... 4 >> checking size of long... 8 >> checking size of long long... 8 >> checking size of __int64... 0 >> checking for ANSI C header files... (cached) yes >> checking float.h usability... yes >> checking float.h presence... yes >> checking for float.h... yes >> checking limits.h usability... yes >> checking limits.h presence... yes >> checking for limits.h... yes >> checking stddef.h usability... yes >> checking stddef.h presence... yes >> checking for stddef.h... yes >> checking for stdlib.h... (cached) yes >> checking for string.h... (cached) yes >> checking sys/time.h usability... yes >> checking sys/time.h presence... yes >> checking for sys/time.h... yes >> checking for stdint.h... (cached) yes >> checking whether byte ordering is bigendian... no >> ----------------------------------------------- >> Default path = /home/kjetil/sage/sage-5.8/local /usr /usr/local >> ----------------------------------------------- >> checking for GMP >= 3.1.1... found >> checking whether GMP is 4.0 or greater... yes >> checking whether GMP was compiled with --enable-cxx... yes >> checking for GIVARO >= 30700 and < 30800... found >> checking "for BLAS (-lcblas -latlas)"... no >> checking for C interface to BLAS with -lcblas... not working >> checking for C interface to BLAS with -lblas... not working >> checking for other BLAS... problem >> Sorry, your BLAS are not working. Disabling. >> >> **************************************************************************** >> *** ERROR: BLAS not found! >> > > It looks to me like you don't have any blas installed or detected, did you try > to use ATLAS from the system? Is there any libblas.* libcblas.* or libatlas.* > in /home/kjetil/sage/sage-5.8/local/lib ? > > Francois > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- "If you want a picture of the future - imagine a boot stamping on the human face - forever." George Orwell (1984) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
