Hi
On Tue, 1 Oct 2019 at 11:50, François Bissey wrote:
> Have you used “SAGE_FAT_BINARY=yes”? it is the only way to make a somewhat
> portable
> binary that doesn’t have the problem you describe.
>
Yes, that works, thanks, I actually just forgot that this time.
Regards,
Jan
--
.~.
/V\
Have you used “SAGE_FAT_BINARY=yes”? it is the only way to make a somewhat
portable
binary that doesn’t have the problem you describe.
> On 1/10/2019, at 10:47 PM, Dima Pasechnik wrote:
>
> looks like you need to pass some flags to NTL,
> apparently it doesn't know what Core 2 CPUs are any more
looks like you need to pass some flags to NTL,
apparently it doesn't know what Core 2 CPUs are any more...
Perhaps reporting this to NTL?
On Tue, Oct 1, 2019 at 5:35 PM Jan Groenewald wrote:
>
> Hi
>
> I have compiled sage 8.9 on a KVM used as a master image for a computer lab.
> The CPU is pres
Hi
I have compiled sage 8.9 on a KVM used as a master image for a computer lab.
The CPU is presented as model name : Intel Xeon E3-12xx v2 (Ivy Bridge)
Imaging is using systemimager based on rsync.
On the newer lab machines with Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
the sage copied to the
