Berker Peksag added the comment:
2.7 now uses libffi 3.1 and our ARM buildbots are quite healthy so I think we
can now close this 'out of date'.
--
nosy: +berker.peksag
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Mark Lawrence added the comment:
Can this be closed as out of date as we're now up to 2.7.7?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12640
___
python272 letters.rando...@gmail.com added the comment:
test_ctypes is successful in 2.7.3rc1, armv7l (using --with-system-ffi
(3.0.10); i haven't tested w/out that config option)
note:
Python-2.7.3rc1/Modules/_ctypes/libffi/configure
contains this line:
VERSION='3.0.10rc0'
(2.7.2 has the
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +amaury.forgeotdarc, belopolsky, meador.inge
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12640
___
python272 letters.rando...@gmail.com added the comment:
problem also occurs when built with configure option --with-system-ffi
not sure whether it might be a compiler bug or an invalid test?
some debug output:
[@localhost Python-2.7.2]$ gdb ./python
(gdb) run -Wd -3 -E -tt
New submission from python272 letters.rando...@gmail.com:
[meego]$/opt/org.python.python-2.7.2/bin/python -m test.regrtest ...
...
test_callback_register_double
(ctypes.test.test_callbacks.SampleCallbacksTestCase) ... Segmentation fault
this is after a native (not cross-compile) configure;
