Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-16 Thread Eric Gourgoulhon
Hi,

Le jeudi 15 février 2018 23:59:09 UTC+1, Andy Howell a écrit :
>
>
> I had problems under 17.04. I think I was missing the fortran compiler. 
> After installing that, it built fine.
>
>
This list of prerequisites to build Sage on Ubuntu is at
https://wiki.sagemath.org/prerequisitesUbuntu
This is currently for Ubuntu 16.04. Let me encourage people taking part in 
this thread to update it to Ubuntu 17.10 and possibly 18.04. 

Best wishes,

Eric.

-- 
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-16 Thread Thierry Dumont
I have an Ubuntu 17.10, and 8.2 beta 5 compiles without anay problems.
May be I must say that I upraded from one version to another with
git pull origin develop
just issuing  make after the git command. But I don't think this could
hide some problem.
Yours
t.d.

-- 
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-16 Thread Andy Howell


On 02/16/2018 02:40 AM, Jeroen Demeyer wrote:
> On 2018-02-15 23:59, Andy Howell wrote:
>> I think you may have something else wrong with your system. I too
>> upgraded from 17.04 to 17.10. I built 8.2beta 3 with no problems. I'm
>> compiling beta 5 right now.
>
> It would be interesting to see the output of
>
> $ ldd /usr/lib/gcc/x86_64-linux-gnu/7.2.0/cc1
>
> on your system. If libmpfr appears twice, it is really a bug in Ubuntu.
>
Looks OK here:

ldd /usr/lib/gcc/x86_64-linux-gnu/7.2.0/cc1
    linux-vdso.so.1 =>  (0x7fff551a7000)
    libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15
(0x7f92bab37000)
    libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3
(0x7f92ba91f000)
    libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4
(0x7f92ba6ba000)
    libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10
(0x7f92ba43a000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f92ba236000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f92ba019000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f92b9cc3000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f92b98e3000)
    /lib64/ld-linux-x86-64.so.2 (0x7f92baebd000)

Andy

-- 
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-16 Thread Jeroen Demeyer

On 2018-02-15 23:59, Andy Howell wrote:

I think you may have something else wrong with your system. I too
upgraded from 17.04 to 17.10. I built 8.2beta 3 with no problems. I'm
compiling beta 5 right now.


It would be interesting to see the output of

$ ldd /usr/lib/gcc/x86_64-linux-gnu/7.2.0/cc1

on your system. If libmpfr appears twice, it is really a bug in Ubuntu.

--
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-16 Thread Jeroen Demeyer

On 2018-02-15 22:37, Harald Helfgott wrote:

First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1

 linux-vdso.so.1 =>  (0x7fff8af56000)
 libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15
(0x7fcb74113000)
 libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3
(0x7fcb73efb000)
 libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4
(0x7fcb73c96000)
 libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10
(0x7fcb73a15000)
 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000)
 libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000)
 /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000)
 libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6
(0x7fcb72c3e000)


To expand on what François said: this is already problematic because it 
links to two different versions of libmpfr. So it has nothing to do with 
Sage, your system compiler is broken. If your GCC package up-to-date in 
Ubuntu?



Do you mean that I will have compile problems when working on my own programs, 
without sage?


Yes, although most programs can be compiled without hitting that bug. In 
Sage, only giac breaks as far as I know.


--
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread Andy Howell
Harald,

I think you may have something else wrong with your system. I too
upgraded from 17.04 to 17.10. I built 8.2beta 3 with no problems. I'm
compiling beta 5 right now.

I had problems under 17.04. I think I was missing the fortran compiler.
After installing that, it built fine.

Andy



On 02/15/2018 04:16 PM, Harald Helfgott wrote:
>
> I typed
>
>     export SAGE_INSTALL_GCC='yes'
>
> and then did "make", and got what looks like exactly the same error at
> exactly the same place. Log file attached.
>
> Le jeudi 15 février 2018 17:01:22 UTC-5, Thierry
> (sage-googlesucks@xxx) a écrit :
>
> Hi,
>
> On Fri, Feb 16, 2018 at 10:56:07AM +1300, François Bissey wrote:
> > 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.
>
> Which can be done by doing
>
> export SAGE_INSTALL_GCC='yes'
>
> before make.
>
> Ciao,
> Thierry
>
>
> >
> > > On 16/02/2018, at 10:37, Harald Helfgott  > wrote:
> > >
> > > First, here is the output of
>  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1
> > >
> > >     linux-vdso.so.1 =>  (0x7fff8af56000)
> > >     libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15
> (0x7fcb74113000)
> > >     libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3
> (0x7fcb73efb000)
> > >     libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4
> (0x7fcb73c96000)
> > >     libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10
> (0x7fcb73a15000)
> > >     libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> (0x7fcb73811000)
> > >     libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
> (0x7fcb735f4000)
> > >     libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
> (0x7fcb7329e000)
> > >     libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> (0x7fcb72ebe000)
> > >     /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000)
> > >     libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6
> (0x7fcb72c3e000)
> > >
> > > Here is the output of the second command:
> > >     linux-vdso.so.1 =>  (0x7ffdd0f78000)
> > >     libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15
> (0x7f6d62321000)
> > >     libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3
> (0x7f6d62109000)
> > >     libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4
> (0x7f6d61ea4000)
> > >     libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10
> (0x7f6d61c23000)
> > >     libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> (0x7f6d61a1f000)
> > >     libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
> (0x7f6d61802000)
> > >     libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
> (0x7f6d614ac000)
> > >     libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> (0x7f6d610cc000)
> > >     /lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000)
> > >     libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6
> (0x7f6d60e4c000)
> > >
> > > 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+...@googlegroups.com .
> > > To post to this group, send email to sage-...@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+...@googlegroups.com .
> > To post to this group, send email 

Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread François Bissey
You would have to either do
* make distclean before typing make
or
* run ./configure before make

> On 16/02/2018, at 11:16, Harald Helfgott  wrote:
> 
> 
> I typed
> 
> export SAGE_INSTALL_GCC='yes' 
> 
> and then did "make", and got what looks like exactly the same error at 
> exactly the same place. Log file attached.
> 
> Le jeudi 15 février 2018 17:01:22 UTC-5, Thierry (sage-googlesucks@xxx) a 
> écrit :
> Hi, 
> 
> On Fri, Feb 16, 2018 at 10:56:07AM +1300, François Bissey wrote: 
> > 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. 
> 
> Which can be done by doing 
> 
> export SAGE_INSTALL_GCC='yes' 
> 
> before make. 
> 
> Ciao, 
> Thierry 
> 
> 
> > 
> > > On 16/02/2018, at 10:37, Harald Helfgott  wrote: 
> > > 
> > > First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd 
> > > cc1 
> > > 
> > > linux-vdso.so.1 =>  (0x7fff8af56000) 
> > > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> > > (0x7fcb74113000) 
> > > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> > > (0x7fcb73efb000) 
> > > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> > > (0x7fcb73c96000) 
> > > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> > > (0x7fcb73a15000) 
> > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000) 
> > > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000) 
> > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000) 
> > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000) 
> > > /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000) 
> > > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> > > (0x7fcb72c3e000) 
> > > 
> > > Here is the output of the second command: 
> > > linux-vdso.so.1 =>  (0x7ffdd0f78000) 
> > > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> > > (0x7f6d62321000) 
> > > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> > > (0x7f6d62109000) 
> > > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> > > (0x7f6d61ea4000) 
> > > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> > > (0x7f6d61c23000) 
> > > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6d61a1f000) 
> > > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6d61802000) 
> > > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6d614ac000) 
> > > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6d610cc000) 
> > > /lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000) 
> > > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> > > (0x7f6d60e4c000) 
> > > 
> > > 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+...@googlegroups.com. 
> > > To post to this group, send email to sage-...@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+...@googlegroups.com. 
> > To post to this group, send email to sage-...@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 

Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread François Bissey
Any code using standard complex header from C or C++, possibly fortran is
likely to break. I would hope ubuntu realise the mistake.

> On 16/02/2018, at 10:59, Harald Helfgott  wrote:
> 
> What should I do, then? Do you mean that I will have compile problems when 
> working on my own programs, without sage?
> 
> Le jeudi 15 février 2018 16:55:25 UTC-5, François Bissey a écrit :
> 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  wrote: 
> > 
> > First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1 
> > 
> > linux-vdso.so.1 =>  (0x7fff8af56000) 
> > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> > (0x7fcb74113000) 
> > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> > (0x7fcb73efb000) 
> > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> > (0x7fcb73c96000) 
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> > (0x7fcb73a15000) 
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000) 
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000) 
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000) 
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000) 
> > /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000) 
> > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> > (0x7fcb72c3e000) 
> > 
> > Here is the output of the second command: 
> > linux-vdso.so.1 =>  (0x7ffdd0f78000) 
> > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> > (0x7f6d62321000) 
> > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> > (0x7f6d62109000) 
> > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> > (0x7f6d61ea4000) 
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> > (0x7f6d61c23000) 
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6d61a1f000) 
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6d61802000) 
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6d614ac000) 
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6d610cc000) 
> > /lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000) 
> > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> > (0x7f6d60e4c000) 
> > 
> > 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+...@googlegroups.com. 
> > To post to this group, send email to sage-...@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.

-- 
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread Thierry
Hi,

On Fri, Feb 16, 2018 at 10:56:07AM +1300, François Bissey wrote:
> 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.

Which can be done by doing

export SAGE_INSTALL_GCC='yes'

before make.

Ciao,
Thierry


> 
> > On 16/02/2018, at 10:37, Harald Helfgott  wrote:
> > 
> > First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1
> > 
> > linux-vdso.so.1 =>  (0x7fff8af56000)
> > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> > (0x7fcb74113000)
> > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> > (0x7fcb73efb000)
> > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> > (0x7fcb73c96000)
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> > (0x7fcb73a15000)
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000)
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000)
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000)
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000)
> > /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000)
> > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> > (0x7fcb72c3e000)
> > 
> > Here is the output of the second command:
> > linux-vdso.so.1 =>  (0x7ffdd0f78000)
> > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> > (0x7f6d62321000)
> > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> > (0x7f6d62109000)
> > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> > (0x7f6d61ea4000)
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> > (0x7f6d61c23000)
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6d61a1f000)
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6d61802000)
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6d614ac000)
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6d610cc000)
> > /lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000)
> > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> > (0x7f6d60e4c000)
> > 
> > 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.

-- 
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] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread Harald Helfgott
What should I do, then? Do you mean that I will have compile problems when 
working on my own programs, without sage?

Le jeudi 15 février 2018 16:55:25 UTC-5, François Bissey a écrit :
>
> 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  > wrote: 
> > 
> > First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd 
> cc1 
> > 
> > linux-vdso.so.1 =>  (0x7fff8af56000) 
> > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> (0x7fcb74113000) 
> > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> (0x7fcb73efb000) 
> > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> (0x7fcb73c96000) 
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> (0x7fcb73a15000) 
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000) 
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000) 
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000) 
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000) 
> > /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000) 
> > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> (0x7fcb72c3e000) 
> > 
> > Here is the output of the second command: 
> > linux-vdso.so.1 =>  (0x7ffdd0f78000) 
> > libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> (0x7f6d62321000) 
> > libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
> (0x7f6d62109000) 
> > libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> (0x7f6d61ea4000) 
> > libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> (0x7f6d61c23000) 
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6d61a1f000) 
> > libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6d61802000) 
> > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6d614ac000) 
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6d610cc000) 
> > /lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000) 
> > libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> (0x7f6d60e4c000) 
> > 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@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.


Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread François Bissey
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  wrote:
> 
> First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1
> 
> linux-vdso.so.1 =>  (0x7fff8af56000)
> libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> (0x7fcb74113000)
> libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 (0x7fcb73efb000)
> libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> (0x7fcb73c96000)
> libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> (0x7fcb73a15000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000)
> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000)
> /lib64/ld-linux-x86-64.so.2 (0x7fcb74499000)
> libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> (0x7fcb72c3e000)
> 
> Here is the output of the second command:
> linux-vdso.so.1 =>  (0x7ffdd0f78000)
> libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
> (0x7f6d62321000)
> libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 (0x7f6d62109000)
> libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
> (0x7f6d61ea4000)
> libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
> (0x7f6d61c23000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6d61a1f000)
> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6d61802000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6d614ac000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6d610cc000)
> /lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000)
> libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
> (0x7f6d60e4c000)
> 
> 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.


Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread Harald Helfgott
First, here is the output of  /usr/lib/gcc/x86_64-linux-gnu/7.2.0$ ldd cc1

linux-vdso.so.1 =>  (0x7fff8af56000)
libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
(0x7fcb74113000)
libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
(0x7fcb73efb000)
libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
(0x7fcb73c96000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7fcb73a15000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fcb73811000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fcb735f4000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fcb7329e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fcb72ebe000)
/lib64/ld-linux-x86-64.so.2 (0x7fcb74499000)
libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
(0x7fcb72c3e000)

Here is the output of the second command:
linux-vdso.so.1 =>  (0x7ffdd0f78000)
libisl.so.15 => /usr/lib/x86_64-linux-gnu/libisl.so.15 
(0x7f6d62321000)
libmpc.so.3 => /usr/lib/x86_64-linux-gnu/libmpc.so.3 
(0x7f6d62109000)
libmpfr.so.4 => /usr/lib/x86_64-linux-gnu/libmpfr.so.4 
(0x7f6d61ea4000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 
(0x7f6d61c23000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f6d61a1f000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f6d61802000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f6d614ac000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f6d610cc000)
/lib64/ld-linux-x86-64.so.2 (0x7f6d626a7000)
libmpfr.so.6 => /usr/lib/x86_64-linux-gnu/libmpfr.so.6 
(0x7f6d60e4c000)

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.


Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread Jeroen Demeyer

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.


Re: [sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread François Bissey


> On 16/02/2018, at 09:34, Harald Helfgott  wrote:
> 
> I have just updated Ubuntu 17.04 to 17.10 (since version 17.04 reached its 
> end-of-life point). Sage was uninstalled in the process. The binary I 
> reinstalled from the standard repositories crashed, so the only option I had 
> left was to install the most recent stable version of Sage (8.1) from source.
> 
> I get: (end of the log file)
> 
> 
> Error installing package giac-1.2.3.47.p0
> 
> Please email sage-devel (http://groups.google.com/group/sage-devel)
> explaining the problem and including the log file
>   /home/ahelfgo/Downloads/sage-8.1/logs/pkgs/giac-1.2.3.47.p0.log
> Describe your computer, operating system, etc.
> If you want to try to fix the problem yourself, *don't* just cd to
> /home/ahelfgo/Downloads/sage-8.1/local/var/tmp/sage/build/giac-1.2.3.47.p0 
> and type 'make' or whatever is appropriate.
> Instead, the following commands setup all environment variables
> correctly and load a subshell for you to debug the error:
>   (cd 
> '/home/ahelfgo/Downloads/sage-8.1/local/var/tmp/sage/build/giac-1.2.3.47.p0' 
> && '/home/ahelfgo/Downloads/sage-8.1/sage' --sh)
> When you are done debugging, you can type "exit" to leave the subshell.
> 
> 
> I am attaching the entire log file for giac. 
> 
> What is the issue here? What can be done?
> 
> Best
> Harald
> harald.helfg...@gmail.com
> PS. The computer is a Dell XPS Ultrabook with the following specifications:
> 
> Memory: 7,7 GiB
> Processor: Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 
> Ubuntu 17.10
> Gnome 3.26.2
> 

This may be interesting. Could you tell me what version of mpfr is installed on 
the 
system? It is needed by gcc.

François

-- 
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.


[sage-devel] SAGE 8.1 will not compile under Ubuntu 17.10: error installing giac-1.2.3.47.p0

2018-02-15 Thread Harald Helfgott
I have just updated Ubuntu 17.04 to 17.10 (since version 17.04 reached its 
end-of-life point). Sage was uninstalled in the process. The binary I 
reinstalled from the standard repositories crashed, so the only option I 
had left was to install the most recent stable version of Sage (8.1) from 
source.

I get: (end of the log file)


Error installing package giac-1.2.3.47.p0

Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /home/ahelfgo/Downloads/sage-8.1/logs/pkgs/giac-1.2.3.47.p0.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/ahelfgo/Downloads/sage-8.1/local/var/tmp/sage/build/giac-1.2.3.47.p0 
and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd 
'/home/ahelfgo/Downloads/sage-8.1/local/var/tmp/sage/build/giac-1.2.3.47.p0' 
&& '/home/ahelfgo/Downloads/sage-8.1/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.


I am attaching the entire log file for giac. 

What is the issue here? What can be done?

Best
Harald
harald.helfg...@gmail.com
PS. The computer is a Dell XPS Ultrabook with the following specifications:

Memory: 7,7 GiB
Processor: Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 
Ubuntu 17.10
Gnome 3.26.2

-- 
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.
Found local metadata for giac-1.2.3.47.p0
Using cached file 
/home/ahelfgo/Downloads/sage-8.1/upstream/giac-1.2.3.47.tar.bz2
giac-1.2.3.47.p0

Setting up build directory for giac-1.2.3.47.p0
Finished extraction
Applying patches from ../patches...
Applying ../patches/cSolveorder-check.patch
patching file check/TP16-sol.cas.out1
Applying ../patches/libpng16.patch
patching file configure.in
patching file configure
Applying ../patches/macos-ifactor.patch
patching file src/ifactor.cc
Applying ../patches/nofltk-check.patch
patching file check/testgeo
patching file check/TP00-sol.cas
patching file check/TP00-sol.cas.out1
patching file check/TP02-sol.cas
patching file check/TP09-sol.cas
patching file check/TP19-sol.cas

Host system:
Linux ahelfgo-XPS-13-9360 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.2.0-8ubuntu3' 
--with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) 

Configuring giac...
configure: WARNING: you should use --build, --host, --target
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix