[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: Another note: mixed endianness might have been a factor as previous versions of the product that were shipped used bi-arch x86 (32-bit userland on 64-bit kernel. -- ___ Python tracker

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: Yes, it's a duplicate. That being said, documentation alone it should be unsigned long for Darwin (OS/X), FreeBSD, OpenBSD. Looking at the definition for ioctl(2), the below example would cause a failure. I need to hunt around for a practical example as I don'

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Serhiy Storchaka added the comment: This looks as a duplicate of issue521723 and issue1471. Do you have tests that demonstrate a failure with using ioctl on OpenBSD? May be there are problems on 64-bit big-endian platforms (or even on 64-bit little-endian if additional parameters are passed to

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Changes by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Changes by Antoine Pitrou : -- nosy: +skrah, trent ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: ... g'night. -- Added file: http://bugs.python.org/file27955/python-issue16124.patch ___ Python tracker ___

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: Grr... Let's try again. -- Added file: http://bugs.python.org/file27954/python-issue16124.patch ___ Python tracker ___ _

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Changes by Garrett Cooper : Removed file: http://bugs.python.org/file27953/python-issue16124.patch ___ Python tracker ___ ___ Python-bugs-list

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: And I missed the int -> unsigned int part. Resubmitting one last time for tonight.. -- Added file: http://bugs.python.org/file27953/python-issue16124.patch ___ Python tracker

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Changes by Garrett Cooper : Removed file: http://bugs.python.org/file27951/python-issue13500-test.patch ___ Python tracker ___ ___ Python-bugs

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: Sorry; previous patch is not applicable to this issue. This one is. -- Added file: http://bugs.python.org/file27952/python-issue16124.patch ___ Python tracker _

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: $ uname -a FreeBSD bayonetta.local 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #0 r240836M: Sat Sep 22 12:30:11 PDT 2012 gcooper@bayonetta.local:/usr/obj/store/freebsd/stable/9/sys/BAYONETTA amd64 $ ./configure --prefix=/scratch/python-bin/3k/ ... $ make all; ma

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Garrett Cooper added the comment: Yes. Submitting a patch to fix this based on hg master shortly.. -- ___ Python tracker ___ ___ Pytho

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

Andrew Svetlov added the comment: Is it affected for 3.3 and 3.4 also? -- nosy: +asvetlov versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___

[issue16124] fcntl_ioctl still not 100% sane with unsigned longs

New submission from Garrett Cooper: As discussed in ID # 1471, the type for request is not 100% correct on some platforms (FreeBSD, NetBSD, and OpenBSD, for instance) and the custom platform that I'm using unfortunately uses non-32-bit int ioctls. An autoconf test needs to be added for these p