[issue7247] test_fcntl_64_bit from test_fcntl.py fails in Python 2.6.4

2011-08-04 Thread Elias Pipping
Elias Pipping added the comment: I had this problem as well. Recompiling my kernel with CONFIG_DNOTIFY=y fixed it (Thanks to David Leverton for pointing this out to me). -- ___ Python tracker <http://bugs.python.org/issue7

[issue7247] test_fcntl_64_bit from test_fcntl.py fails in Python 2.6.4

2011-08-03 Thread Elias Pipping
Changes by Elias Pipping : -- nosy: +pipping ___ Python tracker <http://bugs.python.org/issue7247> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1099] Mac compile fails with pydebug and framework enabled

2011-08-03 Thread Elias Pipping
Changes by Elias Pipping : -- nosy: -pipping ___ Python tracker <http://bugs.python.org/issue1099> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue1099] Mac compile fails with pydebug and framework enabled

2008-08-10 Thread Elias Pipping
Elias Pipping <[EMAIL PROTECTED]> added the comment: Configuring with '--with-pydebug --enable-framework --enable-universalsdk' (and invoking make afterwards) certainly works now for me. I'm running XCode 3.1 -- or more importantly 'i686-apple-darwin9-gcc-4.0.1 (GC

[issue1099] Mac compile fails with pydebug and framework enabled

2007-09-08 Thread Elias Pipping
Elias Pipping added the comment: powerpc : macosx 10.4.10, xcode 2.4.1 (gcc 4.0.1 build 5367) intel : macosx 10.4.10, xcode 2.5pre (gcc 4.0.1 build 5370) __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/

[issue1099] Mac compile fails with pydebug and framework enabled

2007-09-08 Thread Elias Pipping
Elias Pipping added the comment: I can reproduce this problem on both an intel and a powerpc mac. With '--with-pydebug --enable-framework --enable-universalsdk', the behavior is very much different: On a powerpc mac, configure fails with 'checking size of wchar_t...configure