Development version build fails on Windows 7

[Mikko Vanhatalo]

Hello,

I'm trying to build the development version (changeset
1607:2608abe6239a)
on Windows 7 using the supplied instructions. I'm using the prebuilt
Scheme48 1.8 from s48.org and Windows 7 SDK v7.1.

The build fails during the execution of 'build-initial-image.bat', what
it comes down to seems to be:
Warning: undefined variables
#{Package 249 user}
set-port-crlf?!
(&warning)

and later:

Error: undefined variable
set-port-crlf?!
(package user)

I've attached the full log.

I don't have VS Express 2010 installed, but the C compilation
on the next step seems to go just fine using msbuild.

[Michael Sperber]

Post by Mikko Vanhatalo
I'm trying to build the development version (changeset
1607:2608abe6239a)
on Windows 7 using the supplied instructions. I'm using the prebuilt
Scheme48 1.8 from s48.org and Windows 7 SDK v7.1.

Glad to know somebody else but me builds on Windows!

Post by Mikko Vanhatalo
The build fails during the execution of 'build-initial-image.bat', what
Warning: undefined variables
#{Package 249 user}
set-port-crlf?!
(&warning)

Huh, strange: 1.8 has `set-port-crlf?!'. In the Scheme 48 1.8 you're
using to do this, what does this yield, when you type it in the REPL?

,open (subset ports (set-port-crlf?!))
set-port-crlf?!

[Mikko Vanhatalo]

Post by Michael Sperber

Post by Mikko Vanhatalo
I'm trying to build the development version (changeset
1607:2608abe6239a)
on Windows 7 using the supplied instructions. I'm using the prebuilt
Scheme48 1.8 from s48.org and Windows 7 SDK v7.1.

Glad to know somebody else but me builds on Windows!

Post by Mikko Vanhatalo
The build fails during the execution of 'build-initial-image.bat', what
Warning: undefined variables
#{Package 249 user}
set-port-crlf?!
(&warning)

Huh, strange: 1.8 has `set-port-crlf?!'. In the Scheme 48 1.8 you're
using to do this, what does this yield, when you type it in the REPL?
,open (subset ports (set-port-crlf?!))
set-port-crlf?!

It works.

I was running the commands from a SDK CMD prompt, which for some
unknown reason, caused all this. The build run fine from a normal
prompt without the stuff defined by the SDK.

Opening the ports module from both of the prompts succeeded though.