Ticket #106 (new defect)

Opened 21 months ago

Last modified 2 weeks ago

Regression tests fail for Python 2.6 on Win32

Reported by: JimKleckner Owned by: somebody
Priority: major Milestone: 0.14
Component: Testing Keywords: windows
Cc: dalcinl, SamB

Description

8 regression tests fail on Python 2.6 release using Visual Studio 9.0 on Windows XP.

This was run using the changeset 1291:16fc9454a2e5

ERROR: compiling (c) coercearraytoptr
ERROR: compiling (cpp) coercearraytoptr
ERROR: compiling (c) declarations
ERROR: compiling (cpp) declarations
ERROR: compiling (c) excvalcheck
ERROR: compiling (cpp) excvalcheck
ERROR: compiling (c) nogil
ERROR: compiling (cpp) nogil

coercearraytoptr.obj : error LNK2019: unresolved external symbol _spam referenced in function ___pyx_f_16coercearraytoptr_eggs
cython-devel\BUILD\compile\c\coercearraytoptr.pyd : fatal error LNK1120: 1 unresolved externals
coercearraytoptr.obj : error LNK2019: unresolved external symbol _spam referenced in function "void __cdecl __pyx_f_16coercearraytoptr_eggs(void)" (?__pyx_f_16coercearraytoptr_eggs@@YAXXZ)
cython-devel\BUILD\compile\cpp\coercearraytoptr.pyd : fatal error LNK1120: 1 unresolved externals
declarations.obj : error LNK2019: unresolved external symbol _ifnp referenced in function ___pyx_f_12declarations_f
cython-devel\BUILD\compile\c\declarations.pyd : fatal error LNK1120: 1 unresolved externals
declarations.obj : error LNK2019: unresolved external symbol _ifnp referenced in function "void __cdecl __pyx_f_12declarations_f(void)" (?__pyx_f_12declarations_f@@YAXXZ)
cython-devel\BUILD\compile\cpp\declarations.pyd : fatal error LNK1120: 1 unresolved externals
excvalcheck.obj : error LNK2019: unresolved external symbol _tomato referenced in function ___pyx_f_11excvalcheck_eggs
excvalcheck.obj : error LNK2019: unresolved external symbol _grail referenced in function ___pyx_f_11excvalcheck_eggs
excvalcheck.obj : error LNK2019: unresolved external symbol _spam referenced in function ___pyx_f_11excvalcheck_eggs
cython-devel\BUILD\compile\c\excvalcheck.pyd : fatal error LNK1120: 3 unresolved externals
excvalcheck.obj : error LNK2019: unresolved external symbol _tomato referenced in function "void __cdecl __pyx_f_11excvalcheck_eggs(void)" (?__pyx_f_11excvalcheck_eggs@@YAXXZ)
excvalcheck.obj : error LNK2019: unresolved external symbol _grail referenced in function "void __cdecl __pyx_f_11excvalcheck_eggs(void)" (?__pyx_f_11excvalcheck_eggs@@YAXXZ)
excvalcheck.obj : error LNK2019: unresolved external symbol _spam referenced in function "void __cdecl __pyx_f_11excvalcheck_eggs(void)" (?__pyx_f_11excvalcheck_eggs@@YAXXZ)
cython-devel\BUILD\compile\cpp\excvalcheck.pyd : fatal error LNK1120: 3 unresolved externals
nogil.obj : error LNK2019: unresolved external symbol _e2 referenced in function ___pyx_f_5nogil_h
nogil.obj : error LNK2019: unresolved external symbol _e1 referenced in function ___pyx_f_5nogil_h
nogil.obj : error LNK2019: unresolved external symbol _g2 referenced in function ___pyx_f_5nogil_h
cython-devel\BUILD\compile\c\nogil.pyd : fatal error LNK1120: 3 unresolved externals
nogil.obj : error LNK2019: unresolved external symbol "void * __cdecl e2(void)" (?e2@@YAPAXXZ) referenced in function "void __cdecl __pyx_f_5nogil_h(struct _object *)" (?__pyx_f_5nogil_h@@YAXPAU_object@@@Z)
nogil.obj : error LNK2019: unresolved external symbol "void __cdecl e1(void)" (?e1@@YAXXZ) referenced in function "void __cdecl __pyx_f_5nogil_h(struct _object *)" (?__pyx_f_5nogil_h@@YAXPAU_object@@@Z)
nogil.obj : error LNK2019: unresolved external symbol _g2 referenced in function "void __cdecl __pyx_f_5nogil_h(struct _object *)" (?__pyx_f_5nogil_h@@YAXPAU_object@@@Z)
cython-devel\BUILD\compile\cpp\nogil.pyd : fatal error LNK1120: 3 unresolved externals

Change History

Changed 21 months ago by JimKleckner

I guess these tests also fail with 2.5.

Changed 21 months ago by JimKleckner

Hm. It happened on my cygwin-based platform as well.

Changed 21 months ago by JimKleckner

Changed 21 months ago by JimKleckner

Lisandro has checked in this patch:

 http://www.cython.org/hg/cython-devel/rev/5905f7b15cb2

for this Trac item #104

I still get these link errors with cygwin/gcc using cython-dev changeset 1296:96f15e379330:

ERROR: compiling (c) coercearraytoptr
ERROR: compiling (cpp) coercearraytoptr
ERROR: compiling (c) declarations
ERROR: compiling (cpp) declarations
ERROR: compiling (c) excvalcheck
ERROR: compiling (cpp) excvalcheck

Changed 21 months ago by robertwb

  • milestone changed from 0.10 to 0.10.1

Lisandro's patch was for warnings, not errors. Somehow on windows we need to tell it to ignore missing symbols (that would be "found" at runtime).

Changed 21 months ago by robertwb

  • milestone changed from 0.10.1 to 0.11

Changed 18 months ago by robertwb

  • component changed from Parsing to Build System

Short of more details (I don't have a windows computer to test this on) I'm going to move this to a further milestone.

Changed 18 months ago by robertwb

  • milestone changed from 0.11 to 0.11.1

Changed 16 months ago by dalcinl

  • cc dalcinl added

Changed 16 months ago by robertwb

  • milestone changed from 0.11.1 to 0.11.2

Changed 15 months ago by dagss

  • keywords windows added

Changed 15 months ago by dagss

  • milestone changed from 0.11.2 to wishlist

Changed 15 months ago by dagss

  • milestone changed from wishlist to 0.11.3

Changed 10 months ago by robertwb

  • milestone changed from 0.11.3 to 0.12

Changed 9 months ago by robertwb

  • milestone changed from 0.12 to 0.12.1

Changed 8 months ago by SamB

  • cc SamB added

Just where are these symbols supposed to come from? Hint: DLL exports are slightly different in nature from ordinary C symbols...

Changed 6 months ago by robertwb

  • component changed from Build System to Testing

Changed 6 months ago by robertwb

  • milestone changed from 0.12.1 to 0.13

We keep bumping this, it's be nice to get an actual fix...

Changed 2 weeks ago by robertwb

  • milestone changed from 0.13 to 0.14
Note: See TracTickets for help on using tickets.