Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
On 2016-02-22 23:18, Volker Braun wrote: I think you just ran out of RAM Most likely. Note the signal is "Killed", not "Segmentation Fault". So it's probably the out-of-memory killer which killed your gcc. -- 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
On Sunday, February 21, 2016 at 6:23:45 PM UTC, Martin Vahi wrote: > > I tried again. This time with the > > export SAGE_ATLAS_ARCH="base" > > > added to the Bash script. I did not notice any differences at the log > file, although I did not very thoroughly study it, because I'm not the > maintainer of anything in Sage. > which bash script? No need to change any scripts... What was meant is to run $ SAGE_ATLAS_ARCH=base ./sage -f atlas or $ SAGE_ATLAS_ARCH=base $MAKE -- 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
On Sunday, February 21, 2016 at 5:01:35 PM UTC, Volker Braun wrote: > > On Sunday, February 21, 2016 at 11:07:48 AM UTC+1, Jeroen Demeyer wrote: >> >> One possible idea: the path >> /home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0 >> >> >> is unusually long, maybe try a shorter/simpler path? >> > > +1 the atlas tuning code is full of hardcoded directory length limits, > often quite short. > hmm, really? I don't see anything hardcoded like this, only places where strlen(path) is computed and on the basis of the result a malloc is called to allocate memory to store it. -- 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
On Sunday, February 21, 2016 at 11:07:48 AM UTC+1, Jeroen Demeyer wrote: > > One possible idea: the path > /home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0 > > > is unusually long, maybe try a shorter/simpler path? > +1 the atlas tuning code is full of hardcoded directory length limits, often quite short. Alternatively try setting SAGE_ATLAS_ARCH=base to skip tuning. -- 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
On Sunday, February 21, 2016 at 10:07:48 AM UTC, Jeroen Demeyer wrote: > > On 2016-02-21 10:55, Martin Vahi wrote: > > |gcc -fPIC > > > -L/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib > > > > > -Wl,-rpath,/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast > > > > /2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib -m64 > > -DL2SIZE=4194304 > > > -I/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/var/tmp/sage/build/atlas-3.10.2/src/ATLAS-build/include > > > > > -I/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/var/tmp/sage/build/atlas-3.10.2/src/ATLAS-build/../ATLAS//include > > > > > -I/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/var/tmp/sage/build/atlas-3.10.2/src/ATLAS-build/../ATLAS//include/contrib > > > > -DAdd_ -DF77_INTEGER=int -DStringSunStyle -DATL_OS_Linux > > -DATL_ARCH_x86SSE2 -DATL_CPUMHZ=2400 -DATL_SSE2 -DATL_SSE1 > > -DATL_USE64BITS -DATL_GAS_x8664 -m64 -DATL_FULL_LAPACK -DDREAL -o > > ATL_dset_xp1yp0aXbX.o -c ATL_dset_xp1yp0aXbX.c > > gcc: error: > > /2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib: No such > > file or directory > > The problem is that somehow an extra space came in here between > "juur_liivakast" and "/2016_02_xx_Sage_7_0" in the command above. > which could be due to the fact that this is "root of the sandbox" (as my Tallinn-born wife tells me :-)) and somewhere in this kind of virtual(?) environment setting of the sandbox things go wrong... To reproduce this, more details on the setup would be needed, I guess. > One possible idea: the path > /home/ts2/Projektid/progremise_infrastruktuur/matemaatikamlootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0 > > > is unusually long, maybe try a shorter/simpler path? > > Also: please attach the *complete* log file of ATLAS and not an > "excerpt". I say this for 2 reasons: > - very often, the omitted part contains interesting information > - pasting something as text can change the formatting, for example > adding line breaks. > -- 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
On 2016-02-21 10:55, Martin Vahi wrote: |gcc -fPIC -L/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib -Wl,-rpath,/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast /2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib -m64 -DL2SIZE=4194304 -I/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/var/tmp/sage/build/atlas-3.10.2/src/ATLAS-build/include -I/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/var/tmp/sage/build/atlas-3.10.2/src/ATLAS-build/../ATLAS//include -I/home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/var/tmp/sage/build/atlas-3.10.2/src/ATLAS-build/../ATLAS//include/contrib -DAdd_ -DF77_INTEGER=int -DStringSunStyle -DATL_OS_Linux -DATL_ARCH_x86SSE2 -DATL_CPUMHZ=2400 -DATL_SSE2 -DATL_SSE1 -DATL_USE64BITS -DATL_GAS_x8664 -m64 -DATL_FULL_LAPACK -DDREAL -o ATL_dset_xp1yp0aXbX.o -c ATL_dset_xp1yp0aXbX.c gcc: error: /2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0/local/lib: No such file or directory The problem is that somehow an extra space came in here between "juur_liivakast" and "/2016_02_xx_Sage_7_0" in the command above. One possible idea: the path /home/ts2/Projektid/progremise_infrastruktuur/matemaatikamootorid/Sage/juur_liivakast/2016_02_xx_Sage_7_0/bonnet/tmp_/build_dir/sage-7.0 is unusually long, maybe try a shorter/simpler path? Also: please attach the *complete* log file of ATLAS and not an "excerpt". I say this for 2 reasons: - very often, the omitted part contains interesting information - pasting something as text can change the formatting, for example adding line breaks. -- 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
In any case we need more info; Full logs, openSUSE version, glibc and compiler versions, ... On Saturday, February 6, 2016 at 11:51:43 PM UTC+1, Volker Braun wrote: > > 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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
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.
Re: [sage-devel] Re: Failure to Compile Sage 7.0 Stable on openSUSE Linux
Hi, On Fri, Feb 05, 2016 at 11:34:47AM -0800, Martin Vahi wrote: [...] > Since I'm not a Sage developer, that concludes this bug report for me. I > wonder, if it should be re-written to some bug-track or something > similar? I've read that there's quite a specific procedure for filing > those reports. > > Could some of the Sage developers please open a "ticket"? There is nothing like appointed Sage developer. If you feel able or just willing to do something for Sage (like fixing LLVM compilation issues), please ask for a trac account (trac is the bug tracker), open a ticket and do it ! WE NEED YOU ON BOARD! http://doc.sagemath.org/html/en/developer/ Ciao, Thierry -- 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.
