Failure in test-suite/standalone/test-ffi test

[Eli Zaretskii]

This test fails on MS-Windows in the MinGW build as follows:

     Backtrace:
     In ice-9/boot-9.scm:
      157: 11 [catch #t #<catch-closure d9f620> ...]
     In unknown file:
        ?: 10 [apply-smob/1 #<catch-closure d9f620>]
     In ice-9/boot-9.scm:
       63: 9 [call-with-prompt prompt0 ...]
     In ice-9/eval.scm:
      432: 8 [eval # #]
     In ice-9/boot-9.scm:
     2401: 7 [save-module-excursion #<procedure db6c80 at 
ice-9/boot-9.scm:4045:3 ()>]
     4050: 6 [#<procedure db6c80 at ice-9/boot-9.scm:4045:3 ()>]
     1724: 5 [%start-stack load-stack #<procedure ce4900 at 
ice-9/boot-9.scm:4041:10 ()>]
     1729: 4 [#<procedure c0ecd8 ()>]
     In unknown file:
        ?: 3 [primitive-load 
"d:/gnu/guile-2.0.11/test-suite/standalone/test-ffi"]
     In ice-9/eval.scm:
      453: 2 [eval # ()]
      387: 1 [eval # ()]
     In unknown file:
        ?: 0 [dynamic-func "strerror" #<dynamic-object #f>]
   ERROR: In procedure dynamic-func:
     ERROR: In procedure dynamic-pointer: Symbol not found: strerror
     FAIL: test-ffi

Does this test make some unportable assumptions about the 'strerror'
symbol?  Or should I debug this?

TIA