2020-06-23 21:13:16 +0100 received badge ● Famous Question (source) 2019-11-28 18:29:16 +0100 received badge ● Popular Question (source) 2019-11-28 18:29:16 +0100 received badge ● Notable Question (source) 2018-12-16 05:45:10 +0100 received badge ● Enthusiast 2018-12-09 07:43:00 +0100 commented question Issues during sagelib-8.4 building for Raspbian Stretch on armv7l On x86_64, the case is same. 2018-12-04 17:17:29 +0100 commented answer How to pack sage-8.4 armv7l built as compressed re-distributable binaries? Well here is a micro_kernel version torrent link of sage-8.4 armv7l compressed binaries https://drive.google.com/open?id=1GrO... or direct link https://drive.google.com/open?id=13cq... if anyone interested. 2018-12-02 12:48:26 +0100 received badge ● Associate Editor (source) 2018-12-01 16:33:48 +0100 asked a question Issues during sagelib-8.4 building for Raspbian Stretch on armv7l During sagelib-8.4 building for Raspbian Stretch on armv7l/RPI3B as part of sage-8.4 build, some messages appeared which might interest sage developers, https://pastebin.com/KJy0ffXe. In short, the issue is with failure to find cimported module gmpy2 whereas the system has gmpy2 installed, sage-8.4 $pip show gmpy2 Name: gmpy2 Version: 2.0.8 Summary: GMP/MPIR, MPFR, and MPC interface to Python 2.6+ and 3.x Home-page: http://code.google.com/p/gmpy/ Author: Case Van Horsen Author-email: casevh@gmail.com License: UNKNOWN Location: /usr/local/lib/python2.7/dist-packages Requires: Required-by:  But eventually sagelib-8.4 building completes. So how much it limits the functioinality of sagelib-8.4 or it doesn't? And is that avoidable/fixable (workarounds!)? 2018-12-01 08:41:46 +0100 received badge ● Supporter (source) 2018-11-30 21:08:01 +0100 commented answer How to pack sage-8.4 armv7l built as compressed re-distributable binaries? make micro_release did its job but finally prints out a message like "rdfind not installed. Not hardlinking identical files". So rdfind should have been a dependency/prerequisite. 2018-11-30 10:51:07 +0100 received badge ● Scholar (source) 2018-11-29 22:43:11 +0100 received badge ● Nice Question (source) 2018-11-29 12:18:57 +0100 commented question Where to Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent make from removing what has built so far? @Iguananaut among your latest two comments, the former one seems like the answer to my question. Even with the simple make command with export SAGE_KEEP_BUILT_SPKGS=yes starts building the doc from the beginning though the simple make successfully completes the doc building but make -j4 doesn't. And I'll keep in mind your second suggestion. 2018-11-29 10:59:11 +0100 received badge ● Student (source) 2018-11-28 20:23:07 +0100 received badge ● Organizer (source) 2018-11-28 16:00:12 +0100 asked a question How to pack sage-8.4 armv7l built as compressed re-distributable binaries? So I have compiled sage-8.4 for Raspbian Stretch on armv7l/RPI3B and it took size of about 12 GB and now if I want to re-distribute it as compressed re-distributable binaries, which files and folders I can trim down to reduce its size keeping the working condition? sage-8.4$ ls -la total 748 drwxr-xr-x 15 pi pi 4096 Nov 27 15:26 . drwxr-xr-x 40 pi pi 4096 Nov 28 17:37 .. -rw-r--r-- 1 pi pi 44178 Nov 27 13:17 aclocal.m4 drwxr-xr-x 2 pi pi 4096 Nov 27 15:17 autom4te.cache -rwxr-xr-x 1 pi pi 4060 Oct 18 05:13 bootstrap drwxr-xr-x 7 pi pi 4096 Oct 18 05:13 build -rw-r--r-- 1 pi pi 11 Nov 28 13:26 .BUILDSTART drwxr-xr-x 2 pi pi 4096 Oct 18 05:13 .ci drwxr-xr-x 2 pi pi 4096 Oct 18 05:13 .circleci drwxr-xr-x 2 pi pi 4096 Nov 27 15:17 config -rw-r--r-- 1 pi pi 90637 Nov 27 15:18 config.log -rwxr-xr-x 1 pi pi 81382 Nov 27 15:18 config.status -rwxr-xr-x 1 pi pi 295272 Nov 27 15:17 configure -rw-r--r-- 1 pi pi 26587 Oct 18 05:13 configure.ac -rw-r--r-- 1 pi pi 9684 Nov 27 15:18 configure.log -rw-r--r-- 1 pi pi 66986 Oct 18 05:13 COPYING.txt -rw-r--r-- 1 pi pi 252 Oct 18 05:13 .dir-locals.el drwxr-xr-x 3 pi pi 4096 Oct 18 05:13 docker lrwxrwxrwx 1 pi pi 10 Nov 28 17:37 .dockerignore -> .gitignore drwxr-xr-x 8 pi pi 4096 Oct 18 05:16 .git drwxr-xr-x 2 pi pi 4096 Oct 18 05:13 .github -rw-r--r-- 1 pi pi 1058 Oct 18 05:13 .gitignore -rw-r--r-- 1 pi pi 6753 Oct 18 05:13 .gitlab-ci.yml drwxr-xr-x 10 pi pi 4096 Nov 28 14:21 local drwxr-xr-x 3 pi pi 4096 Nov 28 14:21 logs drwxr-xr-x 2 pi pi 4096 Oct 18 05:13 m4 -rw-r--r-- 1 pi pi 7284 Oct 18 05:13 Makefile -rw-r--r-- 1 pi pi 17604 Oct 18 05:13 README.md -rwxr-xr-x 1 pi pi 4756 Oct 18 05:13 sage drwxr-xr-x 9 pi pi 4096 Nov 28 00:48 src drwxr-xr-x 2 pi pi 12288 Oct 18 05:17 upstream -rw-r--r-- 1 pi pi 47 Oct 18 05:13 VERSION.txt  2018-11-28 15:44:39 +0100 commented question Where to Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent make from removing what has built so far? @slelievre the bare ./configure should default to python2 if not specified otherwise and that's my case, i. e. python2 @Iguananaut I tried something like that but i could not exactly understand what the dochtml.log https://pastebin.com/KxscKcMB meant in its messages even after following the suggestion. 2018-11-24 09:40:48 +0100 edited question Where to Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent make from removing what has built so far? I am building sage-8.4 on a RPI3B running Raspbian Stretch and it gets stuck in the documentation compiling section https://pastebin.com/gysZzgW3 and if I terminate and redo the process with make -j4 as before then it says The build directory may contain configuration files and other potentially helpful information. WARNING: if you now run 'make' again, the build directory will, by default, be deleted. Set the environment variable SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. Makefile:31: recipe for target 'all-start' failed make[1]: *** [all-start] Error 1 make[1]: Leaving directory '/home/pi/sage-8.4' Makefile:13: recipe for target 'all' failed make: *** [all] Error 2  So I have been able to avoid the above message by doing \$ ln -sf /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.22 /home/pi/sage-8.4/local/lib/libstdc++.so.6  but then again if I redo the make process, the docs built so far removed and the process starts from beginning of documentation building. So how do I do this? Will just putting export SAGE_KEEP_BUILT_SPKGS=yes in sage-8.4/src/bin/save-env-config suffice and if it does then how to achieve it? so far I failed to make it work.