Summary

csm fails on Windows

Metadata

• Id: 4d4443dd26eb3f78008c0c9941dc04f2117e06f8
• Trac id:
• Type: defect
• Reporter: felix
• Owner: felix
• Cc:
• Status: accepted
• Component: extensions
• Estimated difficulty: medium
• Resolution:
• Priority: major
• Milestone:
• Version: 6.0.0
• Changetime: 2026-08-26 12:35:41 UTC
• Created: 2026-08-23 10:20:43 UTC
• Keywords: csm

Description

(Reported by Quinn Van De Keere:)

I'm trying to compile a simple project via CSM consisting of just one .scm file (for now) and it refuses to work on Windows.

C:/code/avs/code $ csm

  "C:/CHICKEN/bin/csc" "-s" "-J" "-I" "C:/code/avs/code" "-C" "-I" "-C"

"C:/code/avs/code" "C:/code/avs/code\avs.scm" "-o" "avs.so"

The filename, directory name, or volume label syntax is incorrect.

command failed with non-zero exit status: "C:/CHICKEN/bin/csc" "-s" "-J" "-I" "C:/code/avs/code" "-C" "-I" "-C" "C:/code/avs/code" "C:/code/avs/code\avs.scm" "-o" "avs.so"

This command was executed via the w64devkit shell, although it also refuses to work outside that environment (e.g. in powershell or the standard command prompt) with the same error. I tested this same setup in my OpenBSD VM and it works just fine.

Changes and comments

[2026-08-23 10:21:10 UTC] felix set owner to felix

[2026-08-23 10:21:11 UTC] felix changed status from new to accepted

[2026-08-26 12:35:41 UTC] felix wrote:

I think slashification produces inconsistent filenames. csm 0.93 drops windows-specific slash-substitution. Trying to use "sh -c ' ... '" in a replacement for "system" didn't work, for currently unknown reasons. "-g" should produce a workable makefile, but the problem is not solved yet.