[ python-Bugs-1467201 ] size_t warnings on OSX 10.3

[SourceForge.net]

Bugs item #1467201, was opened at 2006-04-09 06:05
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1467201&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Anthony Baxter (anthonybaxter)
Assigned to: Nobody/Anonymous (nobody)
Summary: size_t warnings on OSX 10.3

Initial Comment:
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}


----------------------------------------------------------------------

>Comment By: Neal Norwitz (nnorwitz)
Date: 2006-07-09 21:14

Message:
Logged In: YES 
user_id=33168

Anthony is this still a problem?

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2006-04-09 23:30

Message:
Logged In: YES 
user_id=21627

Sure. The question then is: what is ssize_t, as opposed to
size_t.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2006-04-09 18:56

Message:
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 :-)

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2006-04-09 14:02

Message:
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?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1467201&group_id=5470