I’d say the compiler is in a broken state at the system level. Exactly like what happens in sage after the mpfr upgrade. I think it would be best to build sage’s own gcc here.
> On 16/02/2018, at 10:37, Harald Helfgott <harald.helfg...@gmail.com> wrote: > > First, here is the output of /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1 > > linux-vdso.so.1 => (0x00007fff8af56000) > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 > (0x00007fcb74113000) > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 (0x00007fcb73efb000) > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 > (0x00007fcb73c96000) > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 > (0x00007fcb73a15000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fcb73811000) > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fcb735f4000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fcb7329e000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fcb72ebe000) > /lib64/ld-linux-x86-64.so.2 (0x00007fcb74499000) > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 > (0x00007fcb72c3e000) > > Here is the output of the second command: > linux-vdso.so.1 => (0x00007ffdd0f78000) > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 > (0x00007f6d62321000) > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 (0x00007f6d62109000) > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 > (0x00007f6d61ea4000) > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 > (0x00007f6d61c23000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6d61a1f000) > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6d61802000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6d614ac000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6d610cc000) > /lib64/ld-linux-x86-64.so.2 (0x00007f6d626a7000) > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 > (0x00007f6d60e4c000) > > What to do? > > Best > Harald > > Le jeudi 15 février 2018 16:18:18 UTC-5, Jeroen Demeyer a écrit : > On 2018-02-15 21:34, Harald Helfgott wrote: > > What is the issue here? What can be done? > > Seems like a conflict between the mpfr/mpc libraries used by your > system's GCC and the libraries in Sage. > > Can you try to find the location of the "cc1" program used by GCC. > Typically, this will be in a location like > /usr/libexec/gcc/x86_64-pc-linux-gnu/4.9.4/cc1 and then do (adjusting > the paths) > > $ ldd /usr/libexec/gcc/x86_64-pc-linux-gnu/4.9.4/cc1 > > And from the Sage directory: > > $ ./sage --sh -c "ldd /usr/libexec/gcc/x86_64-pc-linux-gnu/4.9.4/cc1" > > and post the output of both commands. > > -- > 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. -- 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.
