Hi all,

here are my current results of building the spur versions on Windows, using commit 16ffd5b + patch from #498 (comment)

• cygwin32/cygwin64 for build.win32x86:

  $ ./mvm -f
  <lots of output with exit code zero>
  $ ./build/vm/SqueakConsole ..\relative\path\to\valid\squeak.image
  Could not open the Squeak image file <C:\absolute\path\to\valid\squeak.image>
  <...>
  Aborting...
  Smalltalk stack dump:
  <end of output>

• cygwin32 for build.win64x64:

  $ ./mvm -f
  <lots of output with exit code zero>
  $ ./build/vm/SqueakConsole ..\relative\path\to\valid\squeak.image
  <no output>

• cygwin64 for build.win64x64:

  $ ./mvm -f
  <less but still a lot of output>
  rm: cannot remove 'build/vm/ADPCMCodecPlugin.lib': No such file or directory
  make[1]: [/cygdrive/c/Users/Christoph/OneDrive/Dokumente/Squeak/Christoph/git/opensmalltalk-vm/build.win64x64/common/Makefile.plugin:139: build/vm/ADPCMCodecPlugin.lib] Error 1 (ignored)
  x86_64-w64-mingw32-ar rc build/vm/ADPCMCodecPlugin.lib build/ADPCMCodecPlugin/ADPCMCodecPlugin.o
  make[1]: x86_64-w64-mingw32-ar: No such file or directory
  make[1]: *** [/cygdrive/c/Users/Christoph/OneDrive/Dokumente/Squeak/Christoph/git/opensmalltalk- vm/build.win64x64/common/Makefile.plugin:140: build/vm/ADPCMCodecPlugin.lib] Error 127
  make[1]: Leaving directory „/cygdrive/c/Users/Christoph/OneDrive/Dokumente/Squeak/Christoph/git/opensmalltalk- vm/build.win64x64/squeak.cog.spur“
  make: *** [../common/Makefile:271: build/vm/ADPCMCodecPlugin.lib] Error 2
  <exit code nonzero>

Additional notes:

• When I run SqueakConsole.exe from Cygwin, the output listed above is appended by a "Segmentation fault" line. When run in PowerShell, this line is not displayed, but everything else looks identically.
• Running Squeak.exe (without "Console") did not work better, but as is known does not log errors to the console.
• Despite I passed the image path to the executable, I have to choose it manually in a dialog.
• Same problems when using squeak.stack.spur instead of squeak.cog.spur. So this is not a JIT problem (is this correct?).

If anyone succeeds to build, we should really encapsulate the necessary tech stack. I believe this could make things really easier ... 😅

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.