Sage build/upgrade complete!
Dear leif thank you so much for the workaround.
On Friday, September 2, 2016 at 6:36:57 PM UTC+2, Simon Brandhorst wrote:
>
> After renaming the libomalloc.so
>
> Successfully installed singular-3.1.7p1.p2
>
> There were a bunch of warnings in the log but i guess
After renaming the libomalloc.so
Successfully installed singular-3.1.7p1.p2
There were a bunch of warnings in the log but i guess that is okay...
I'll try and build the rest now.
On Friday, September 2, 2016 at 6:07:56 PM UTC+2, leif wrote:
>
> leif wrote:
> > Simon Brandhorst wrote:
> >>
[singular-3.1.7p1.p2]
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:186:
undefined reference to `fmpz_get_mpz'
[singular-3.1.7p1.p2]
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/factory/FLINTconvert.cc:187:
leif wrote:
> Simon Brandhorst wrote:
>> I did it triple-safe.
>> Doesn't seem to work. Here is the log.
>
> As guessed, the sizeof(long) test fails due to a runtime linker error.
> (Singular's 'configure' uses all libs found so far even in unrelated
> tests, and you seem to have some libomalloc
Simon Brandhorst wrote:
> I did it triple-safe.
> Doesn't seem to work. Here is the log.
As guessed, the sizeof(long) test fails due to a runtime linker error.
(Singular's 'configure' uses all libs found so far even in unrelated
tests, and you seem to have some libomalloc system-wide which it
leif wrote:
> leif wrote:
>> Simon Brandhorst wrote:
>>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>>> laptop to work - so I could not get the log until now.
>>
>> Never mind. Please post / attach
>>
I did it triple-safe.
Doesn't seem to work. Here is the log.
-simon
On Friday, September 2, 2016 at 1:48:46 AM UTC+2, leif wrote:
>
> leif wrote:
> > leif wrote:
> >> Simon Brandhorst wrote:
> >>> Thank you leif. Sorry for taking so long to answer. I did not bring my
> >>> laptop to work -
leif wrote:
> leif wrote:
>> Simon Brandhorst wrote:
>>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>>> laptop to work - so I could not get the log until now.
>>
>> Never mind. Please post / attach
>>
leif wrote:
> Simon Brandhorst wrote:
>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>> laptop to work - so I could not get the log until now.
>
> Never mind. Please post / attach
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
leif wrote:
> Simon Brandhorst wrote:
>> Thank you leif. Sorry for taking so long to answer. I did not bring my
>> laptop to work - so I could not get the log until now.
>
> Never mind. Please post / attach
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
Simon Brandhorst wrote:
> Thank you leif. Sorry for taking so long to answer. I did not bring my
> laptop to work - so I could not get the log until now.
Never mind. Please post / attach
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
.
> A workaround would
Thank you leif. Sorry for taking so long to answer. I did not bring my
laptop to work - so I could not get the log until now.
A workaround would be great. Then I can get started.
Tried to build sage devel at work and got a different error. Should I open
a thread for that as well? (If it works
Dima Pasechnik wrote:
> not sure whether it's worth the trouble fighting with outdated Singular
> package refusing to work with
> gcc 6.1.1. Perhaps it might be easier to use the bleeding edge
> https://trac.sagemath.org/ticket/17635 and
> https://trac.sagemath.org/ticket/17254
Well, he was
On Thursday, September 1, 2016 at 8:48:13 AM UTC, leif wrote:
>
> Simon Brandhorst wrote:
> > So here are the logs. And a larger bit of the install.log
>
> Thanks, but we'd need the config.log files from Singular, not Sage's
> top-level one, in your case:
>
>
leif wrote:
> Simon Brandhorst wrote:
>> So here are the logs. And a larger bit of the install.log
>
> Thanks, but we'd need the config.log files from Singular, not Sage's
> top-level one, in your case:
>
> /home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
>
>
Simon Brandhorst wrote:
> So here are the logs. And a larger bit of the install.log
Thanks, but we'd need the config.log files from Singular, not Sage's
top-level one, in your case:
/home/simon/sage/local/var/tmp/sage/build/singular-3.1.7p1.p2/src/latest/config.log
and since omalloc takes an
So here are the logs. And a larger bit of the install.log
singular-3.1.7p1.p2] loading cache .././config.cache
[singular-3.1.7p1.p2] checking whether make -j1 sets ${MAKE}... (cached) yes
[singular-3.1.7p1.p2] checking for gcc... (cached) gcc
[singular-3.1.7p1.p2] checking whether the C compiler
Dear leif, dear Nils,
Thank you for your replies.
> That's obviously wrong. It should get 8 there. You might want to do a:
>
> $ grep "size of long" install.log
>
$grep "size of long" install.log
[python2-2.7.10.p2] checking size of long... 8
[python2-2.7.10.p2] checking size of long long... 8
Simon Brandhorst wrote:
> So far I am using precompiled binaries. They work. Now I am thinking on
> writing my own branch/contributing to sage so I followed the instructions on
>
> http://doc.sagemath.org/html/en/developer/walk_through.html
>
> to get a developer version of sage.
> Basically I
On Wednesday, August 31, 2016 at 12:38:51 PM UTC-7, Simon Brandhorst wrote:
>
> So far I am using precompiled binaries. They work. Now I am thinking on
> writing my own branch/contributing to sage so I followed the instructions on
>
> http://doc.sagemath.org/html/en/developer/walk_through.html
>
Just in case some more hardware details:
Architecture: x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list: 0-7
Thread(s) per core:2
Core(s) per socket:4
Socket(s): 1
NUMA node(s): 1
21 matches
Mail list logo
