On Thu, Mar 14, 2019 at 5:44 PM Ai Bo wrote:
>
> I see. Thank you.
> As I don't know how and when the files will be cleaned on the local disk and
> I don't know when my program, if launched at local disk, will be killed.
A typical HPC center policy with scratch disks is that files live a
certain
I see. Thank you.
As I don't know how and when the files will be cleaned on the local disk
and I don't know when my program, if launched at local disk, will be killed.
I downloaded the binary package. I am a little bit confused. Does the
binary package know where I already build ./sage?
On Thu, M
On Thu, Mar 14, 2019 at 7:24 AM Dima Pasechnik wrote:
>
> On Thu, Mar 14, 2019 at 7:09 AM Dima Pasechnik wrote:
> >
> > On Thu, Mar 14, 2019 at 3:39 AM Ai Bo wrote:
> > >
> > > Sorry, it doesn't work if I build on local disk and then copy to /nfs.
> > > I got error:
> > > bash-4.3$ ./sage
>
> Bu
On Thu, Mar 14, 2019 at 7:09 AM Dima Pasechnik wrote:
>
> On Thu, Mar 14, 2019 at 3:39 AM Ai Bo wrote:
> >
> > Sorry, it doesn't work if I build on local disk and then copy to /nfs.
> > I got error:
> > bash-4.3$ ./sage
But did you try moving it back to the local disk, before starting it?
Indeed
On Thu, Mar 14, 2019 at 3:39 AM Ai Bo wrote:
>
> Sorry, it doesn't work if I build on local disk and then copy to /nfs.
> I got error:
> bash-4.3$ ./sage
>
> ERROR: The Sage installation tree has moved
>
> from /tmp/.../sage-8.6
> to /nfs/.../Sage/sage-8.6
>
> This is not supported, and Sage wi
Sorry, it doesn't work if I build on local disk and then copy to /nfs.
I got error:
bash-4.3$ ./sage
ERROR: The Sage installation tree has moved
from /tmp/.../sage-8.6
to /nfs/.../Sage/sage-8.6
This is not supported, and Sage will not work. To install Sage from a
binary package:
As I mention
I see. Will try. Thank you.
On Wed, Mar 13, 2019 at 11:04 AM Dima Pasechnik wrote:
> On Wed, Mar 13, 2019 at 5:57 PM Ai Bo wrote:
> >
> > Sorry, I can't. All local disks are cleaned out every 30 days.
>
> but building does not take that long. :-)
> Besides, once you have a working build you can
On Wed, Mar 13, 2019 at 5:57 PM Ai Bo wrote:
>
> Sorry, I can't. All local disks are cleaned out every 30 days.
but building does not take that long. :-)
Besides, once you have a working build you can, with a bit of effort, move it
around.
>
> On Wed, Mar 13, 2019 at 9:43 AM Dima Pasechnik wrot
Sorry, I can't. All local disks are cleaned out every 30 days.
On Wed, Mar 13, 2019 at 9:43 AM Dima Pasechnik wrote:
> On Wed, Mar 13, 2019 at 4:18 PM Ai Bo wrote:
> >
> > Yes. This is done on NFS.
> > I can't build on local disks as this is not on a particular machine. But
> I do own my own NF
Yes. I meant Cocalc.
My Linux OS is customized. So I am not sure I can use pre-compiled one.
Here is my OS info:
uname -s
Linux
uname -i
x86_64
uname -o
GNU/Linux
On Wed, Mar 13, 2019 at 9:59 AM E. Madison Bray
wrote:
> On Wed, Mar 13, 2019 at 5:18 PM Ai Bo wrote:
> >
> > Yes. This is done
On Wed, Mar 13, 2019 at 5:18 PM Ai Bo wrote:
>
> Yes. This is done on NFS.
> I can't build on local disks as this is not on a particular machine. But I do
> own my own NFS disks.
> Also, the reason I want to build on my machine as when I use the online
> version(server), a long running program w
On Wed, Mar 13, 2019 at 4:18 PM Ai Bo wrote:
>
> Yes. This is done on NFS.
> I can't build on local disks as this is not on a particular machine. But I do
> own my own NFS disks.
Normally multi-user systems have a "scratch" partition, a local disk
reserved for this kind of jobs, which is not bac
Yes. This is done on NFS.
I can't build on local disks as this is not on a particular machine. But I
do own my own NFS disks.
Also, the reason I want to build on my machine as when I use the online
version(server), a long running program will be paused from time to time. I
want to run on some machi
On Wed, Mar 13, 2019 at 4:58 PM Dima Pasechnik wrote:
>
> By looking at the output it looks as if the build it on an NFS, and this is
> known to be severely broken. Could you do the build on a local disk?
Oh, nice catch. Yes, many build tools can have problems on NFS,
especially on older kernel
By looking at the output it looks as if the build it on an NFS, and this is
known to be severely broken. Could you do the build on a local disk?
On Wed, 13 Mar 2019 15:44 E. Madison Bray, wrote:
> On Wed, Mar 13, 2019 at 4:40 AM Ai Bo wrote:
> >
> > Just compiled sage from source code on Linux.
On Wed, Mar 13, 2019 at 4:40 AM Ai Bo wrote:
>
> Just compiled sage from source code on Linux.
> When I launched ./sage, I can do simple math like 2+2 which give correct
> But when I type:
> sage: import sage.graphs
>
> sage: print("%d" % len(list(graphs.nauty_geng("8"
>
> sage: print("%d" % l
Just compiled sage from source code on Linux.
When I launched ./sage, I can do simple math like 2+2 which give correct
But when I type:
sage: import sage.graphs
sage: print("%d" % len(list(graphs.nauty_geng("8"
sage: print("%d" % len(list(graphs(8
I got 0 for both which are not as expec
17 matches
Mail list logo
