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: size_t warnings on OSX 10.3
Type: behavior Stage: test needed
Components: Build Versions: Python 3.1, Python 2.6
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: ajaksu2, anthonybaxter, christian.heimes, loewis, nnorwitz, ronaldoussoren, tim.peters
Priority: low Keywords:

Created on 2006-04-09 13:05 by anthonybaxter, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
mac.buildlog anthonybaxter, 2006-04-09 13:05
Messages (8)
msg28164 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2006-04-09 13:05
Building on my mac, running
sam% uname -a
Darwin sam.local 7.9.0 Darwin Kernel Version 7.9.0: Wed
Mar 30 20:11:17 PST 2005;
root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC  Power
Macintosh powerpc
sam% gcc -v
Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1640)

I get a whole pile of warnings, like the following:
Python/exceptions.c: In function
`UnicodeEncodeError__str__':
Python/exceptions.c:1340: warning: signed size_t
format, Py_ssize_t arg (arg 4)
Python/exceptions.c:1349: warning: signed size_t
format, Py_ssize_t arg (arg 3)
Python/exceptions.c:1349: warning: signed size_t
format, int arg (arg 4)

Attached is full build log. config.status says
"HAVE_SSIZE_T" is defined.
${ac_dA}HAVE_SSIZE_T${ac_dB}HAVE_SSIZE_T${ac_dC}1${ac_dD}
msg28165 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-04-09 21:02
Logged In: YES 
user_id=21627

Can you find out what Py_ssize_t is eventually defined as
(i.e. how is ssize_t defined); how is size_t defined
(looking at the preprocessor output might help)? What type
would the compiler accept for a signed size_t format?
msg28166 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2006-04-10 01:56
Logged In: YES 
user_id=31435

Since Anthony reported that config.status says HAVE_SSIZE_T
is defined, doesn't

#ifdef HAVE_SSIZE_T
typedef ssize_t		Py_ssize_t;

in pyport.h rule here?  Pretty bizarre, if so :-)
msg28167 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-04-10 06:30
Logged In: YES 
user_id=21627

Sure. The question then is: what is ssize_t, as opposed to
size_t.
msg28168 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2006-07-10 04:14
Logged In: YES 
user_id=33168

Anthony is this still a problem?
msg59788 - (view) Author: Christian Heimes (christian.heimes) * (Python committer) Date: 2008-01-12 04:56
*PING*

Is this still a problem, Anthony?
msg87714 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2009-05-13 21:53
Unless someone can confirm the warnings still exist, this will be closed.
msg92320 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2009-09-06 13:36
The warning does not occur on recent versions of OSX (10.5, 10.6), 
therefore closing the issue.
History
Date User Action Args
2022-04-11 14:56:16adminsetgithub: 43180
2009-09-06 13:36:32ronaldoussorensetstatus: open -> closed

nosy: + ronaldoussoren
messages: + msg92320

resolution: out of date
2009-05-13 21:53:25ajaksu2setstatus: pending -> open
priority: normal -> low
type: behavior

versions: + Python 2.6, Python 3.1, - Python 2.5
nosy: + ajaksu2

messages: + msg87714
stage: test needed
2008-01-12 04:56:01christian.heimessetstatus: open -> pending
nosy: + christian.heimes
messages: + msg59788
2006-04-09 13:05:06anthonybaxtercreate