Jonathan Worthington <[EMAIL PROTECTED]> wrote:OK, with the attached patch (which feels kinda hacky, but works) the build completes. That's the good news. The bad news is that almost all of the dynclasses tests fail. Here's an example of what I'm seeing:-libparrot.def : error LNK2001: unresolved external symbol Parrot_setflag
Obsolete API - isn't existing anymore. Removed.
--
# Failed test (t\dynclass\pyint.t at line 497)
t\dynclass\pyint....NOK 21# got: 'Illegal PMC enum (0) in new
# '
# expected: '-13 -13
# '
# '(cd . && .\parrot.exe -b --gc-debug "C:\Documents and Settings\Jonathan.SERVE
R\Desktop\POW\parrot\t\dynclass\pyint_21.imc")' failed with exit code 1
t\dynclass\pyint....NOK 22# Failed test (t\dynclass\pyint.t at line 519)
# got: 'Illegal PMC enum (0) in new
# '
# expected: '3 3 3 3
# '
# '(cd . && .\parrot.exe -b --gc-debug "C:\Documents and Settings\Jonathan.SERVE
R\Desktop\POW\parrot\t\dynclass\pyint_22.imc")' failed with exit code 1
# Failed test (t\dynclass\pyint.t at line 548)
# got: 'Illegal PMC enum (0) in new
# '
# expected: '44 44 44
# '
# '(cd . && .\parrot.exe -b --gc-debug "C:\Documents and Settings\Jonathan.SERVE
R\Desktop\POW\parrot\t\dynclass\pyint_23.imc")' failed with exit code 1
--
Any ideas about what's wrong or suggestions for where I should start digging? I know that the various DLLs built by the dynclasses makefile finish up in runtime/parrot/dynext. Don't know if this means anything, but all of the library tests pass, suggesting the problem isn't with Parrot locating the libraries.
Thanks,
Jonathan
dynclasses_2.diff
Description: Binary data