Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Martin v. Löwis
> (also, as I understand it, the latest ctypes issues seem to have popped up > after > an update of the bundled libffi, so perhaps that update wasn't totally right, > didn't choose the right libffi version, or missed some files?) In the case of the SPARC issue: the bug is still exists in the libf

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Antoine Pitrou
Martin v. Löwis v.loewis.de> writes: > > >> Instead of submitting a bug report, it would be better to submit a > > > > In *addition* to submitted a bug report, surely. :) > > I'm not so sure. It's a ctypes/libffi bug, so most likely, nobody will > be able to fix it when reported. It's probably

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Jeroen Ruigrok van der Werven
-On [20100407 16:17], "Martin v. Löwis" (mar...@v.loewis.de) wrote: >I'm not so sure. It's a ctypes/libffi bug, so most likely, nobody will >be able to fix it when reported. For platform-specific libffi bugs, the >patch most likely will come from the submitter, as nobody else might >have access to

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Martin v. Löwis
>> Instead of submitting a bug report, it would be better to submit a > > In *addition* to submitted a bug report, surely. :) I'm not so sure. It's a ctypes/libffi bug, so most likely, nobody will be able to fix it when reported. For platform-specific libffi bugs, the patch most likely will come

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread exarkun
On 01:29 pm, mar...@v.loewis.de wrote: Mark Dickinson wrote: On Wed, Apr 7, 2010 at 1:39 PM, Jeroen Ruigrok van der Werven wrote: Before I file a bug report, is anyone else seeing this (in my case on FreeBSD 8): Modules/_ctypes/libffi/src/x86/sysv.S:360: Error: junk at end of line, first unr

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Jeroen Ruigrok van der Werven
-On [20100407 15:29], "Martin v. Löwis" (mar...@v.loewis.de) wrote: >Instead of submitting a bug report, it would be better to submit a >patch, though. Can you try having the build process use freebsd.S >instead of sysv.S? Mark and me are looking at it right now. I can compile ctypes using --with

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Martin v. Löwis
Mark Dickinson wrote: > On Wed, Apr 7, 2010 at 1:39 PM, Jeroen Ruigrok van der Werven > wrote: >> Before I file a bug report, is anyone else seeing this (in my case on >> FreeBSD 8): >> >> Modules/_ctypes/libffi/src/x86/sysv.S:360: Error: junk at end of line, first >> unrecognized character is `@

Re: [Python-Dev] ffi junk messages

2010-04-07 Thread Mark Dickinson
On Wed, Apr 7, 2010 at 1:39 PM, Jeroen Ruigrok van der Werven wrote: > Before I file a bug report, is anyone else seeing this (in my case on > FreeBSD 8): > > Modules/_ctypes/libffi/src/x86/sysv.S:360: Error: junk at end of line, first > unrecognized character is `@' > Modules/_ctypes/libffi/src/

[Python-Dev] ffi junk messages

2010-04-07 Thread Jeroen Ruigrok van der Werven
Before I file a bug report, is anyone else seeing this (in my case on FreeBSD 8): Modules/_ctypes/libffi/src/x86/sysv.S:360: Error: junk at end of line, first unrecognized character is `@' Modules/_ctypes/libffi/src/x86/sysv.S:387: Error: junk at end of line, first unrecognized character is `@'