> But to what libraries is Chicken linked in each case? That could be the > source of the discrepancy (does Chicken link to Windows-specific libs > when compiled for Windows? Or different versions of libraries?)
$ ldd /c/Users/markj/dev/lisp/chicken/aoc-chicken/build/advent2015.exe ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ff8519b0000) KERNEL32.DLL => /c/Windows/System32/KERNEL32.DLL (0x7ff8507a0000) KERNELBASE.dll => /c/Windows/System32/KERNELBASE.dll (0x7ff84f640000) msvcrt.dll => /c/Windows/System32/msvcrt.dll (0x7ff850a30000) libchicken.dll => /usr/local/bin/libchicken.dll (0x7ff803b40000) ADVAPI32.dll => /c/Windows/System32/ADVAPI32.dll (0x7ff850e30000) sechost.dll => /c/Windows/System32/sechost.dll (0x7ff851750000) RPCRT4.dll => /c/Windows/System32/RPCRT4.dll (0x7ff850860000) USER32.dll => /c/Windows/System32/USER32.dll (0x7ff84ffa0000) win32u.dll => /c/Windows/System32/win32u.dll (0x7ff84f180000) GDI32.dll => /c/Windows/System32/GDI32.dll (0x7ff850a00000) gdi32full.dll => /c/Windows/System32/gdi32full.dll (0x7ff84f4e0000) msvcp_win.dll => /c/Windows/System32/msvcp_win.dll (0x7ff84f0e0000) ucrtbase.dll => /c/Windows/System32/ucrtbase.dll (0x7ff84f910000) WS2_32.dll => /c/Windows/System32/WS2_32.dll (0x7ff850990000)