CM.make is unable to handle filenames that contain a backslash #245
Labels
bug
Something isn't working
cm
problem with compilation manager
fixed-in-2022.1
issue is fixed in the 2022.1 release
gforge
bug (or feature request) ported from smlnj-gforge repository
Version
110.99.2
Operating System
OS Version
No response
Processor
Any
Component
Compilation manager (CM)
Severity
Cosmetic
Description of the problem
CM.make somehow treats a backslash as a forward slash. This means that CM.make is unable to read any files that have a backslash in their name. For example:
[scanning /.cm]
uncaught exception Io [Io: openIn failed on "/.cm", No such file or directory]
raised at: Basis/Implementation/IO/text-io-fn.sml:792.25-792.71
../cm/util/safeio.sml:30.11
../cm/parse/parse.sml:502.47
Transcript
No response
Expected Behavior
No response
Steps to Reproduce
No response
Additional Information
No response
Email address
No response
Comments from smlnj-gforge
Original smlnj-gforge bug number 312
Submitted on 2022-57-20 at 15:5700
comment by @JohnReppy on 2022-49-31 15:4900 +000 UTC
The problem is that CM is interpreting the backslash as a path separator (which it is on Windows). The interpretation of the argument probably should follow the system's conventions. ~ Note that there is a workaround, which is creating a wrapper CM file that uses a quoted path "\.cm".
comment by @JohnReppy on 2022-02-05 18:0200 +000 UTC
Fixed for 110.99.3 and 2022.2.
The text was updated successfully, but these errors were encountered: