The memcpy declaration is not picked up even though the configure test 
found it, this seems more like a bug in glibc than the compiler. From the 
log:

./string.h:276:5: warning: incompatible implicit declaration of built-in 
function 'memcpy'
     memcpy( libGAP_CHARS_STRING(string), (cstr), tmp_len ); \
     ^


On Saturday, February 6, 2016 at 11:00:12 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-02-04 18:50, Martin Vahi wrote: 
> > 
> > The compilation of the Sage 7.0 was with LLVM, not GCC. 
>
> Are you sure? The log file says 
>
> C compiler: gcc 
> C compiler version: 
> Using built-in specs. 
> COLLECT_GCC=gcc 
> COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.8/lto-wrapper 
> Target: x86_64-suse-linux 
> Configured with: ../configure --prefix=/usr --infodir=/usr/share/info 
> --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 
> --enable-languages=c,c++,objc,fortran,obj-c++,java,ada 
> --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.8 
> --enable-ssp --disable-libssp --disable-plugin 
> --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' 
> --disable-libgcj --disable-libmudflap --with-slibdir=/lib64 
> --with-system-zlib --enable-__cxa_atexit 
> --enable-libstdcxx-allocator=new --disable-libstdcxx-pch 
> --enable-version-specific-runtime-libs --enable-linker-build-id 
> --enable-linux-futex --program-suffix=-4.8 --without-system-libunwind 
> --with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux 
> --host=x86_64-suse-linux 
> Thread model: posix 
> gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) 
>

-- 
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to