Yes, it works!
Thanks again, Francois and Isuru.
Best regards,
Darij
On Thu, Mar 9, 2017 at 2:28 PM, Darij Grinberg wrote:
> Hi Francois,
>
> Ah! I see now. I started compiling in my office, then it failed
> and I tried fixing it via ssh. But I ran ssh on a different server.
> Will try
Hi Francois,
Ah! I see now. I started compiling in my office, then it failed
and I tried fixing it via ssh. But I ran ssh on a different server.
Will try again from my office now.
Best regards and thanks for solving the riddle,
Darij
On Thu, Mar 9, 2017 at 2:22 PM, François Bissey
wrote
On 10/03/17 09:18, Darij Grinberg wrote:
> Hi,
>
> On Thu, Mar 9, 2017 at 2:16 PM, Isuru Fernando wrote:
>> Can you also attach the ntl log?
>
> Here it goes: https://dl.dropboxusercontent.com/u/83265276/ntl-10.1.0.log
>
> Best regards,
> Darij
>
Sorry for the echo. Would you be using ice
Hum, that's definitely a signal that ntl has been compiled with
-std=c++11 and eclib doesn't. Which is strange because I put code
in configure to make sure it would pick up the c++11 bit myself.
I probably didn't take into account a corner case.
On the other hand I think eclib should just switch to
Hi,
On Thu, Mar 9, 2017 at 2:16 PM, Isuru Fernando wrote:
> Can you also attach the ntl log?
Here it goes: https://dl.dropboxusercontent.com/u/83265276/ntl-10.1.0.log
Best regards,
Darij
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To u
Hi,
Can you also attach the ntl log?
Isuru Fernando
On Fri, Mar 10, 2017 at 1:31 AM, Darij Grinberg
wrote:
> Hi Isuru,
>
> thank you. I'm recompiling now (after make distclean) and hitting a
> similar-looking problem:
> https://dl.dropboxusercontent.com/u/83265276/eclib-20170104.log
>
> Could
Hi Isuru,
thank you. I'm recompiling now (after make distclean) and hitting a
similar-looking problem:
https://dl.dropboxusercontent.com/u/83265276/eclib-20170104.log
Could it be that some parts of the compilation use sage's gcc while others
use the system gcc? Is there a way to force them all
Hi,
Did you upgrade your gcc between compiling ntl and compiling giac? It seems
to me like ntl was compiled with gcc 4.x while you are trying to compile
giac with gcc 5.x.
Isuru Fernando
On Wed, Mar 8, 2017 at 8:37 PM, Darij Grinberg
wrote:
> Hi,
>
> I'm failing to build ("make build") 7.6.bet
Hi,
I'm failing to build ("make build") 7.6.beta6 on my university computer:
[giac-1.2.2.103] /home/dgrinber/sage-7.5.1/local/lib/libntl.so: undefined
reference to `vtable for std::__cxx11::basic_stringbuf, std::allocator >@GLIBCXX_3.4.21'
[giac-1.2.2.103] collect2: error: ld returned 1 exit sta
