Hi all,
I just built Poly/ML fixes-5.2.2 (687b32704fdaffe013427962238482b786b666a4) fresh on a new machine with the following setup: uname -a Linux lemma 4.0.0-2-amd64 #1 SMP Debian 4.0.8-1 (2015-07-11) x86_64 GNU/Linux
Now, if I go to a directory with non-lowercase name, I get a bad result: ramana at lemma:~$ mkdir TEST ramana at lemma:~$ cd TEST ramana at lemma:~/TEST$ poly Poly/ML 5.5.3 Testing
OS.Path.mkCanonical(OS.FileSys.getDir());
val it = "/home/ramana/test": string
Why does Poly/ML think it is OK to lowercase filenames on this platform?
Cheers, Ramana
I just realised I was _not_ on fixes-5.5.2 (although the SHA of the commit I gave was correct).
So, the question is: why does master get this wrong?
But I'm not so bothered now, since I know master occasionally breaks.
On 15 October 2015 at 14:43, Ramana Kumar <ramana at member.fsf.org> wrote:
Hi all,
I just built Poly/ML fixes-5.2.2 (687b32704fdaffe013427962238482b786b666a4) fresh on a new machine with the following setup: uname -a Linux lemma 4.0.0-2-amd64 #1 SMP Debian 4.0.8-1 (2015-07-11) x86_64 GNU/Linux
Now, if I go to a directory with non-lowercase name, I get a bad result: ramana at lemma:~$ mkdir TEST ramana at lemma:~$ cd TEST ramana at lemma:~/TEST$ poly Poly/ML 5.5.3 Testing
OS.Path.mkCanonical(OS.FileSys.getDir());
val it = "/home/ramana/test": string
Why does Poly/ML think it is OK to lowercase filenames on this platform?
Cheers, Ramana
On 15/10/2015 04:45, Ramana Kumar wrote:
I just realised I was _not_ on fixes-5.5.2 (although the SHA of the commit I gave was correct).
So, the question is: why does master get this wrong?
A bug; now fixed. Thanks for letting me know.
Actually, I'm just wondering if configure should check for "git" and set the start-up message to indicate the git commit number. That way it would be clear whether it's master or a release version. David