Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Christian Stump
Following the setting of SAGE_CRTI_DIR in "build/pkgs/gcc/spkg-configure.m4" seems to work: (sage-sh) stumpcl2@dlp762:sage$ echo $CC gcc (sage-sh) stumpcl2@dlp762:sage$ echo $CRTI (sage-sh) stumpcl2@dlp762:sage$ CRTI=`$CC -print-file-name=crti.o 2>/dev/null || true` (sage-sh) stumpcl2@dlp762:sa

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Christian Stump
No, it hasn't. I just did "make distclean" and then "./configure" which recreated src/bin/sage-env-config, but it says export SAGE_CRTI_DIR="@SAGE_CRTI_DIR@" -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] subs bug in fraction field (critical)

2019-06-04 Thread Daniel Krenn
I believe I have found a very serious issue in fraction field substitution, see https://trac.sagemath.org/ticket/27933 I find this very critical, so we should try to fix it soon... Best, Daniel PS: I just spent two days of debugging my computations just to narrow it down to such an unexpected b

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Matthias Koeppe
The bad symlink there was probably generated when you didn't regenerate "configure". Could you check that this time SAGE_CRTI_DIR has been correctly substituted in src/bin/sage-env-config (and local/bin/sage-env-config)? On Tuesday, June 4, 2019 at 9:44:21 PM UTC-7, Matthias Koeppe wrote: > > S

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Matthias Koeppe
Something went really wrong there with the symbolic linking script that I added in https://git.sagemath.org/sage.git/commit/?id=73be6cf53f30b53e5a8a3dedf8f30c2c9960475a On Tuesday, June 4, 2019 at 11:30:22 AM UTC-7, Christian Stump wrote: > > [stumpcl2@dlp762 ~]$ cd progs/sage/ > [stumpcl2@dlp7

Re: [sage-devel] MacOS build Sage libcurl error for R

2019-06-04 Thread Emily R
Thanks Dima, the command worked perfectly for me. -- 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, s

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Christian Stump
[stumpcl2@dlp762 ~]$ cd progs/sage/ [stumpcl2@dlp762 sage]$ ls -l local/lib/gcc/*/7.2.0/*crt* -rw-r--r-- 1 stumpcl2 15301 2896 4. Jun 16:22 local/lib/gcc/x86_64-pc-linux-gnu/7.2.0/crtbegin.o -rw-r--r-- 1 stumpcl2 15301 3224 4. Jun 16:22 local/lib/gcc/x86_64-pc-linux-gnu/7.2.0/crtbeginS.o -rw-r-

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Matthias Koeppe
What does ls -l local/lib/gcc/*/7.2.0/*crt* say On Tuesday, June 4, 2019 at 11:12:01 AM UTC-7, Christian Stump wrote: > > here comes > > > /tmp/stumpcl2/sage/local/var/tmp/sage/build/mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0/src/config.log > -- You received this message because

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Christian Stump
here comes /tmp/stumpcl2/sage/local/var/tmp/sage/build/mpir-3.0.0-644faf502c56f97d9accd301965fc57d6ec70868.p0/src/config.log -- 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

Re: [sage-devel] Re: compiling error for 8.8.beta6 on Red Hat 6.10

2019-06-04 Thread Matthias Koeppe
On Tuesday, June 4, 2019 at 7:32:01 AM UTC-7, Christian Stump wrote: > > I finally got > > [gcc-7.2.0] Successfully installed gcc-7.2.0 > > using Matthias' solution. Unfortunately, then the next build of mpir-3.0.0 > fails with "no compiler found" (with and without the --with-mp=mpir flag > set)

Re: [sage-devel] Polyhedron -- make constructions respect backend

2019-06-04 Thread 'Jonathan Kliem' via sage-devel
I have started #27926. I think I leave the base ring business as it is for now. I belive it is taken care of in many (if not all) places, where the base ring of the vertices might differ. Am Dienstag, 4. Juni 2019 11:20:07 UTC+2 schrieb jplab: > > Hi Jonathan, > > Le lundi 3 juin 2019 23:31:29

Re: [sage-devel] Re: error building sage for Scientific Linux 7.6

2019-06-04 Thread Dima Pasechnik
On Mon, Jun 3, 2019 at 10:29 PM Charles Campbell wrote: > > > > Hello: I do have a skylake architecture (10-core, i9-7900X), and the > assembler is as: GNU assembler version 2.27-34.base.el7. your GNU assempler (released in 2016) https://mirror.koddos.net/gnu/binutils/ is older than your CPU (re

Re: [sage-devel] Polyhedron -- make constructions respect backend

2019-06-04 Thread jplab
Hi Jonathan, Le lundi 3 juin 2019 23:31:29 UTC+2, vdelecroix a écrit : > > To my mind: > > * backend and base ring should be preserved by default. Of course > it should make sense: a translation by sqrt(2) would break the > base ring QQ. > +1 > * no need to create one ticket for