I did a little follow up on this. The problem already exists at the
level of the unix interface:
* (setf fid (unix:unix-open "smallOut" unix:o_rdonly unix:r_ok))
7
* (setf fid (unix:unix-open "ann500K.500.e5" unix:o_rdonly unix:r_ok))
NIL
*
However, a small C program can use open to open either file:
#include <stdio.h>
int main(int argc, char **argv) {
int fd;
fd = open(argv[1], "r");
printf("Tried to open %s, fd = %d.\n", argv[1], fd);
return 0;
}
(compiled this, and...)
rif@oscar:~/Projects/SpeakerRecog/NIST98$ C/testopen smallOut
Tried to open smallOut, fd = 3.
rif@oscar:~/Projects/SpeakerRecog/NIST98$ C/testopen ann500K.500.e5
Tried to open ann500K.500.e5, fd = 3.
Also, perl will open and read from ann500K.500.e5 without complaints.
So I don't think it's a Unix or filesystem problem per se, I think it
is CMUCL-related somehow. I'm open to other ideas of course.
Cheers,
rif