[Bug 57570] New: Syntax Error in CMD Batch Parsing
https://bugs.winehq.org/show_bug.cgi?id=57570 Bug ID: 57570 Summary: Syntax Error in CMD Batch Parsing Product: Wine-staging Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juan3(a)yandex.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 77673 --> https://bugs.winehq.org/attachment.cgi?id=77673 running wine cmd When attempting to run the `msys2_shell.cmd` script from MSYS2, Wine fails with a syntax error: `Syntax error: unexpected IN`. This issue occurs during the batch file parsing phase. 1. Download the MSYS2 base archive from the following link: ``` https://github.com/msys2/msys2-installer/releases/download/2024-12-08/msys2-... ``` 2. Extract the archive to a directory, e.g., `Z:\msys2\msys64`. 3. Navigate to the extracted directory: ``` Z:\msys2\msys64> ``` 4. Run the `msys2_shell.cmd` script with the following arguments: ``` msys2_shell.cmd -here -defterm -no-start ``` 5. Observe the error: ``` Syntaxfehler Syntax error: unexpected IN ``` The `msys2_shell.cmd` script should execute without errors and launch the MSYS2 shell environment. Wine fails with a syntax error: `Syntax error: unexpected IN`. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57570 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |cmd Product|Wine-staging |Wine -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57570 Eric Pouech <eric.pouech(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eric.pouech(a)gmail.com --- Comment #1 from Eric Pouech <eric.pouech(a)gmail.com> --- Created attachment 77674 --> https://bugs.winehq.org/attachment.cgi?id=77674 patch confirming attached patch should solve the parsing error (at least parsing up to launching bash.exe is ok now, but as I didn't install the full msys2 package cannot tell if further errors are present. if so, feel free to open another ticket) TIA -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57570 --- Comment #2 from nicolas <juan3(a)yandex.com> --- Created attachment 77677 --> https://bugs.winehq.org/attachment.cgi?id=77677 after patch Now bash.exe hangs but that's another bug -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57570 --- Comment #3 from nicolas <juan3(a)yandex.com> --- Yeah after figuring it out how to compile with a patch it is true that there is no more syntax error, thank you. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57570 Joel Holdsworth <joel(a)airwebreathe.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joel(a)airwebreathe.org.uk -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57570 Bernhard Übelacker <bernhardu@mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu@mailbox.org --- Comment #4 from Bernhard Übelacker <bernhardu@mailbox.org> --- In my development tree I ran the "msys2_shell.cmd -here -defterm -no-start", and got no error. Also the preliminary patch seems to be contained in https://gitlab.winehq.org/wine/wine/-/commit/c0895df1bd4137d2a1479bf1494fe5b... Should therefore this bug marked as resolved-fixed? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=57570 Alexandre Julliard <julliard@winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Alexandre Julliard <julliard@winehq.org> --- Closing bugs fixed in 11.0-rc3. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (3)
-
WineHQ Bugzilla -
WineHQ Bugzilla -
WineHQ Bugzilla