Could you post config.log from gf2xx build directory please?

On Sunday, October 13, 2013 10:06:32 AM UTC+2, Dr David Kirkby wrote:
>
> drkirkby@hawk:~/unsets/sage-5.13.beta0$ ./sage -i gf2x-1.1.p0 
> This looks like the first time you are running Sage. 
> Updating various hardcoded paths... 
> (Please wait at most a few minutes.) 
> DO NOT INTERRUPT THIS. 
> Done updating paths. 
> Found package gf2x-1.1.p0 in spkg/standard/gf2x-1.1.p0.spkg 
> gf2x-1.1.p0 
> ==================================================== 
> Extracting package 
> /export/home/drkirkby/unsets/sage-5.13.beta0/spkg/standard/gf2x-1.1.p0.spkg 
>
> -rw-r--r--   1 drkirkby staff     408440 Aug 20 09:05 
> /export/home/drkirkby/unsets/sage-5.13.beta0/spkg/standard/gf2x-1.1.p0.spkg 
>
> Finished extraction 
> **************************************************** 
> Host system: 
> SunOS hawk 5.11 snv_134 i86pc i386 i86pc 
> **************************************************** 
> C compiler: gcc 
> C compiler version: 
> Using built-in specs. 
> COLLECT_GCC=gcc 
> COLLECT_LTO_WRAPPER=/export/home/drkirkby/unsets/sage-5.13.beta0/local/libexec/gcc/i386-pc-solaris2.11/4.7.3/lto-wrapper
>  
>
> Target: i386-pc-solaris2.11 
> Configured with: ../src/configure 
> --prefix=/export/home/drkirkby/unsets/sage-5.13.beta0/local 
> --with-local-prefix=/export/home/drkirkby/unsets/sage-5.13.beta0/local 
> --with-gmp=/export/home/drkirkby/unsets/sage-5.13.beta0/local 
> --with-mpfr=/export/home/drkirkby/unsets/sage-5.13.beta0/local 
> --with-mpc=/export/home/drkirkby/unsets/sage-5.13.beta0/local 
> --with-system-zlib --disable-multilib --disable-nls 
> Thread model: posix 
> gcc version 4.7.3 (GCC) 
> **************************************************** 
> patching file Makefile.am 
> patching file Makefile.in 
> Configuring gf2x. 
> checking build system type... i386-pc-solaris2.11 
> checking host system type... i386-pc-solaris2.11 
> checking target system type... i386-pc-solaris2.11 
> checking for a BSD-compatible install... /usr/bin/ginstall -c 
> checking whether build environment is sane... yes 
> checking for a thread-safe mkdir -p... config/install-sh -c -d 
> checking for gawk... gawk 
> checking whether make -j12 sets $(MAKE)... yes 
> checking how to print strings... print -r 
> checking for style of include used by make -j12... GNU 
> 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 dependency style of gcc... gcc3 
> checking for a sed that does not truncate output... /usr/bin/gsed 
> checking for grep that handles long lines and -e... /usr/bin/ggrep 
> checking for egrep... /usr/bin/ggrep -E 
> checking for fgrep... /usr/bin/ggrep -F 
> checking for ld used by gcc... ld 
> checking if the linker (ld) is GNU ld... no 
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -p 
> checking the name lister (/usr/bin/nm -p) interface... BSD nm 
> checking whether ln -s works... yes 
> checking the maximum length of command line arguments... 786240 
> checking whether the shell understands some XSI constructs... yes 
> checking whether the shell understands "+="... yes 
> checking how to convert i386-pc-solaris2.11 file names to 
> i386-pc-solaris2.11 format... func_convert_file_noop 
> checking how to convert i386-pc-solaris2.11 file names to toolchain 
> format... func_convert_file_noop 
> checking for ld option to reload object files... -r 
> checking for objdump... no 
> checking how to recognize dependent libraries... pass_all 
> checking for dlltool... no 
> checking how to associate runtime and link libraries... print -r -- 
> checking for archiver @FILE support... no 
> checking for strip... strip 
> checking for ranlib... ranlib 
> checking command to parse /usr/bin/nm -p output from gcc object... ok 
> checking for sysroot... no 
> checking for mt... mt 
> checking if mt is a manifest tool... no 
> checking how to run the C preprocessor... cpp 
> 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 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... no 
> 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) supports shared libraries... yes 
> checking whether -lc should be explicitly linked in... no 
> checking dynamic linker characteristics... solaris2.11 ld.so 
> checking how to hardcode library paths into programs... immediate 
> checking whether stripping libraries is possible... no 
> checking if libtool supports shared libraries... yes 
> checking whether to build shared libraries... yes 
> checking whether to build static libraries... yes 
> checking for gcc... (cached) gcc 
> checking whether we are using the GNU C compiler... (cached) yes 
> checking whether gcc accepts -g... (cached) yes 
> checking for gcc option to accept ISO C89... (cached) none needed 
> checking dependency style of gcc... (cached) gcc3 
> checking whether we are using the GNU C++ compiler... yes 
> checking whether g++ accepts -g... yes 
> checking dependency style of g++... gcc3 
> checking how to run the C++ preprocessor... g++ -E 
> checking for ld used by g++... ld 
> checking if the linker (ld) is GNU ld... no 
> checking whether the g++ linker (ld) 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... no 
> 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) supports shared libraries... yes 
> checking dynamic linker characteristics... solaris2.11 ld.so 
> checking how to hardcode library paths into programs... immediate 
> checking warning verbosity option... -Wall -W for C++ -Wall -W for C 
> checking for gcc option to accept ISO C99... -std=gnu99 
> checking build system compiler gcc -std=gnu99... yes 
> checking for build system executable suffix... 
> checking whether gcc -std=gnu99 and cc understand -c and -o together... 
> yes 
> checking size of unsigned long... 4 
> checking whether gcc -std=gnu99 can compile and run sse-2 code... yes 
> checking whether gcc -std=gnu99 can compile pclmulqdq and if it is 
> supported by the hardware... no 
> configure: using ABI="default" 
> configure:       CC="gcc -std=gnu99" 
> configure:       CFLAGS="-O2 -g  -Wall -W" 
> configure:       CPPFLAGS="" 
> configure:       hwdir="x86_sse2" 
> checking the number of bits in an unsigned long... configure: error: 
> test program failed 
> Error: Failed to configure gf2x. 
>
> real    0m3.132s 
> user    0m0.990s 
> sys    0m1.043s 
> ************************************************************************ 
> Error installing package gf2x-1.1.p0 
> ************************************************************************ 
>
> So I guess whoever wrote the bit of code for testing the number of 
> bits in an unsigned long, had made an error. An upstream issue? 
>
> Dave 
>

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to