Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CM.make is unable to handle filenames that contain a backslash #253

Closed
1 of 5 tasks
JohnReppy opened this issue Jul 15, 2022 · 0 comments
Closed
1 of 5 tasks

CM.make is unable to handle filenames that contain a backslash #253

JohnReppy opened this issue Jul 15, 2022 · 0 comments
Assignees
Labels
bug Something isn't working cm problem with compilation manager fixed-in-110.99.3 issues that will be fixed in the 110.99.3 version gforge bug (or feature request) ported from smlnj-gforge repository

Comments

@JohnReppy
Copy link
Contributor

JohnReppy commented Jul 15, 2022

Version

110.99.2

Operating System

  • All
  • Linux
  • macOS
  • Windows
  • Other Unix

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:

- CM.make "\\.cm";
[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-05-20 at 15:57:00

comment by @JohnReppy on 2022-05-31 15:49:00 +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-06-05 18:02:00 +000 UTC

Fixed for 110.99.3 and 2022.2.

@JohnReppy JohnReppy added bug Something isn't working cm problem with compilation manager gforge bug (or feature request) ported from smlnj-gforge repository labels Jul 15, 2022
@JohnReppy JohnReppy added the fixed-in-110.99.3 issues that will be fixed in the 110.99.3 version label Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cm problem with compilation manager fixed-in-110.99.3 issues that will be fixed in the 110.99.3 version gforge bug (or feature request) ported from smlnj-gforge repository
Projects
None yet
Development

No branches or pull requests

2 participants