It seems that CCL/ARM doesn't like certain filesystems. Specifically in my testing, GlusterFS.
I have a GlusterFS filesystem set up. The ARM system itself is a contributor to this GlusterFS, and has it mounted at /mnt/gluster.
I installed CCL in a directory on /mnt/gluster, and it is able to come up and run. I.e. it is able to open its core image from this filesystem.
But Lisp itself cannot open files stored on the GlusterFS. I always get a "file not found" error.
In reading up on this, it seems like there may be a rational reason for it. GlusterFS exposes a 64-bit filesystem, and 32-bit apps can have a problem with this, it seems.
In CCL's case because it is successfully reading its core image from this FS, but not able to read Lisp file, I submit it as a bug.
It seems that CCL/ARM doesn't like certain filesystems. Specifically in my testing, GlusterFS.
I have a GlusterFS filesystem set up. The ARM system itself is a contributor to this GlusterFS, and has it mounted at /mnt/gluster. I installed CCL in a directory on /mnt/gluster, and it is able to come up and run. I.e. it is able to open its core image from this filesystem.
But Lisp itself cannot open files stored on the GlusterFS. I always get a "file not found" error.
In reading up on this, it seems like there may be a rational reason for it. GlusterFS exposes a 64-bit filesystem, and 32-bit apps can have a problem with this, it seems.
In CCL's case because it is successfully reading its core image from this FS, but not able to read Lisp file, I submit it as a bug.