Issue 10054: select extension does not build on platforms where uintptr_t is provided in inttypes.h (original) (raw)

Issue10054

Created on 2010-10-09 08:10 by akitada, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg118251 - (view)	Author: Akira Kitada (akitada) *	Date: 2010-10-09 08:10
Some platforms have uintptr_t in inttypes.h but Python bulid system assumes it's defined in stdint.h and it causes build failure: """ building 'select' extension gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I/usr/local/include -I/usr/home/akitada/ src/release27-maint/Include -I/usr/home/akitada/src/release27-maint -c /usr/home/akitada/src/release27-maint/Modules/selectmodule.c -o build/temp.freebsd-4. 11-RELEASE-i386-2.7/usr/home/akitada/src/release27-maint/Modules/selectmodule.o /usr/home/akitada/src/release27-maint/Modules/selectmodule.c:1189: #error uintptr_t does not match void *! """
msg118252 - (view)	Author: Akira Kitada (akitada) *	Date: 2010-10-09 08:14
This patch fixes this.
msg118302 - (view)	Author: Akira Kitada (akitada) *	Date: 2010-10-10 04:18
It seems this problem was introduced by a patch in . 3.1 branch does not have this problem because that patch was not applied to release31-maint. Is this intentional?
msg118319 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2010-10-10 08:22
> 3.1 branch does not have this problem because that patch was not > applied to release31-maint. Is this intentional? I don't remember, I suppose it feared it could be an incompatible change or perhaps cause build problems. Anyway, I committed your patch in 3.2 (r85349), 2.7 (r85350) and even 3.1 (r85351). Thank you!