Antoine Pitrou pit...@free.fr added the comment:
Well, it merely means that OpenSSL has changed the const-ness of some of their
APIs over time. As I said I see no warnings with the most recent OpenSSL
versions. Buildbots will tell you the same story: for example, no warnings
under OS X Snow
Antoine Pitrou pit...@free.fr added the comment:
I don't get any warnings with gcc -Wall and OpenSSL 1.0.x.
--
nosy: +pitrou
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2973
Daniel Black dan...@cacert.org added the comment:
out of date?
still occurs on:
AMD64 Leopard 2.7: http://www.python.org/dev/buildbot/all/builders/AMD64
Leopard 2.7/builds/308/steps/compile/logs/warnings (57)
PPC Leopard 2.7: http://www.python.org/dev/buildbot/all/builders/PPC Leopard
Florent Xicluna florent.xicl...@gmail.com added the comment:
On Gentoo buildbots (2.x and 3.x), there's still the same compiler warnings:
http://www.python.org/dev/buildbot/all/builders/x86%20gentoo%20trunk/builds/5899
/home/buildslave/python-trunk/trunk.norwitz-x86/build/Modules/_ssl.c:706:
Barry A. Warsaw ba...@python.org added the comment:
Because we're in release candidate mode, I reverted the change to the
release26-maint branch. It doesn't seem critical enough to sneak in between rc
and final. Please do re-apply after 2.6.5 final is released though!
--
nosy:
STINNER Victor victor.stin...@haypocalc.com added the comment:
barry Because we're in release candidate mode,
barry I reverted the change to the release26-maint branch.
Yeah, sorry. I realized that after backporting the fix to 2.6.
barry Please do re-apply after 2.6.5 final is released
STINNER Victor victor.stin...@haypocalc.com added the comment:
I commited grooverdan's patch: r78596 (trunk), r78597 (2.6), r78598 (py3k),
78599 (3.1).
The API was changed in... 2004, 6 years ago! I hope that everybody upgraded to
the new OpenSSL version since that. Anyway, the warning should
Changes by STINNER Victor victor.stin...@haypocalc.com:
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2973
___
Florent Xicluna la...@yahoo.fr added the comment:
Still occurs on dev and py3k.
And patch applies correctly.
--
nosy: +flox
versions: -Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2973
Florent Xicluna la...@yahoo.fr added the comment:
It occurs on Debian Lenny AMD64.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2973
___
___
Daniel Black dan...@cacert.org added the comment:
The changeset that changed the definitions is here:
http://cvs.openssl.org/chngview?cn=12024 (2004-Mar-14 23:15:13 (UTC))
As you can see there is no easy identifier in the changeset (i'm not
sure how portable an ifdef on a typedef is (possible
Daniel Diniz aja...@gmail.com added the comment:
Would HEADER_ASN1_MAC_H or IMPLEMENT_ASN1_ENCODE_FUNCTIONS_const_fname help?
--
nosy: +ajaksu2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2973
Bill Janssen [EMAIL PROTECTED] added the comment:
Any progress here? I haven't yet found a formulation which suppresses
the warning on all platforms. I'm guessing there will have to be some
kind of cpp test
#if SOMEFEATURE
#define D2I_PARAMETER_2_TYPE unsigned char *
#else
#define
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Yes, although I have no idea what that feature may be... (sigh) Oh well,
it's a wish.
--
priority: normal - low
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2973
Alexander Belopolsky [EMAIL PROTECTED] added the comment:
It looks like this comes from r59493 which purports to fix a warning:
r59493 | christian.heimes | 2007-12-13 23:38:13 -0500 (Thu, 13 Dec 2007)
| 1 line
Fixed
15 matches
Mail list logo
