This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: select extension does not build on platforms where uintptr_t is provided in inttypes.h
Type: compile error Stage: resolved
Components: Build Versions: Python 3.2, Python 2.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: akitada, pitrou
Priority: normal Keywords: patch

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

Files
File name Uploaded Description Edit
issue10054.diff akitada, 2010-10-09 08:14
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 issue7211.
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) * (Python committer) 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!
History
Date User Action Args
2022-04-11 14:57:07adminsetgithub: 54263
2010-10-10 08:22:14pitrousetstatus: open -> closed
resolution: fixed
messages: + msg118319

stage: resolved
2010-10-10 06:53:47ned.deilysetnosy: + pitrou
2010-10-10 04:18:23akitadasetmessages: + msg118302
versions: + Python 3.2
2010-10-09 08:14:02akitadasetfiles: + issue10054.diff
keywords: + patch
messages: + msg118252
2010-10-09 08:10:52akitadacreate