From: Brian M. <br...@ma...> - 2007-07-02 01:31:29
|
I really don't remember where the discussion of the NUL device issues on Win32 left off, but it is getting quite bothersome that the SB-MD5 tests fail for this reason when SB-MD5 actually works just fine. Is there any objection to a change to the test which would make it work on Win32? What is the preferred solution to the NUL (and other DOS device) issue? I remember a chain in which James Knight proposed using the Windows device root \\?\ - is this still applicable? Is there another way we can specify access to these devices, perhaps with a different pathname host? Thanks, -- Brian Mastenbrook br...@ma... http://brian.mastenbrook.net/ |
From: Yaroslav K. <kav...@tu...> - 2007-07-02 05:46:58
|
Brian Mastenbrook wrote: > I really don't remember where the discussion of the NUL device issues on > Win32 left off, but it is getting quite bothersome that the SB-MD5 tests > fail for this reason when SB-MD5 actually works just fine. Is there any > objection to a change to the test which would make it work on Win32? > sb-md5 is builded and testet on win32 without errors. Show log, please. -- WBR, Yaroslav Kavenchuk. |
From: Brian M. <br...@ma...> - 2007-07-04 14:58:13
|
Yaroslav Kavenchuk wrote: > Brian Mastenbrook wrote: >> I really don't remember where the discussion of the NUL device issues >> on Win32 left off, but it is getting quite bothersome that the SB-MD5 >> tests fail for this reason when SB-MD5 actually works just fine. Is >> there any objection to a change to the test which would make it work >> on Win32? >> > > sb-md5 is builded and testet on win32 without errors. Show log, please. > Are you building under cygwin or MSYS? I use the latter, and for me (open "NUL" :direction :input) results in an error. Test SB-MD5-TESTS::SB-MD5.MD5SUM-FILE.0 failed Form: (STRING= (FORMAT NIL "~(~{~2,'0X~}~)" (COERCE (SB-MD5:MD5SUM-FILE "nul") 'LIST)) "d41d8cd98f00b204e9800998ecf8427e") Expected value: T Actual value: #<SB-INT:SIMPLE-FILE-ERROR {AB23C69}>. ; in: LAMBDA NIL ; SB-KERNEL:FLOAT-WAIT ; ; note: deleting unreachable code SB-MD5-TESTS::SB-MD5.MD5SUM-SEQUENCE.ERROR.0 1 out of 236 total tests failed: SB-MD5-TESTS::SB-MD5.MD5SUM-FILE.0.unhandled SIMPLE-ERROR: test-op failed -- Brian Mastenbrook br...@ma... http://brian.mastenbrook.net/ |
From: Yaroslav K. <kav...@tu...> - 2007-07-04 20:22:11
|
Brian Mastenbrook wrote: > Are you building under cygwin or MSYS? I use the latter, and for me > (open "NUL" :direction :input) results in an error. $ uname -a MINGW32_NT-5.1 HOME 1.0.11(0.46/3/2) 2007-01-12 12:05 i686 Msys from build log: ... Doing 236 pending tests of 236 tests total. SB-MD5-TESTS::SB-MD5.RFC1321.ONE-SHOT.0 ... SB-MD5-TESTS::SB-MD5.OTHER.FILL-POINTER.70 SB-MD5-TESTS::SB-MD5.MD5SUM-FILE.0 SB-MD5-TESTS::SB-MD5.MD5SUM-SEQUENCE.ERROR.0 No tests failed.; What is the error with manual test run? * (require :sb-md5) ; loading system definition from ; C:\gnu\local\lib\sbcl\sb-rotate-byte\sb-rotate-byte.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM SB-ROTATE-BYTE {B1F3931}> as SB-ROTATE-BYTE ("SB-ROTATE-BYTE" "SB-MD5") * (STRING= (FORMAT NIL "~(~{~2,'0X~}~)" (COERCE (SB-MD5:MD5SUM-FILE "nul") 'LIST)) "d41d8cd98f00b204e9800998ecf8427e") T * -- WBR, Yaroslav Kavenchuk. |