Sébastien Sablé
added the comment:
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: The Written Word (Albert Chin) (tww-china)
Assigned to: Nobody/Anonymous (nobody)
Summary: semaphore
New submission from
Sébastien Sablé
:
There used to be a bug open concerning this problem in the old bug
tracker but I can't find it in the new bug tracker:
http://mail.python.org/pipermail/python-bugs-list/2005
Changes by
Sébastien Sablé
:
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1234>
__
___
Sébastien Sablé
added the comment:
I can confirm that this bug is still present in Python 2.4.1 (and
probably later versions) on AIX 5.2 and 5.3.
When HAVE_BROKEN_POSIX_SEMAPHORES is not defined at compile time, Python
Sébastien Sablé added the comment:
The bug is still present in Python 2.5.1. The same patch applies.
The patch is rather trivival, could someone please integrate it in trunk?
Thanks in advance
__
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/
Sébastien Sablé added the comment:
I got this problem again this morning while compiling pywin32.
This problem is not specific to me, anyone using Visual Studio 2010 to compile
Python is experiencing the same issue:
http://nukeit.org/compile-python-2-7-packages-with-visual-studio-2010
Sébastien Sablé added the comment:
I had the same issue today. The patch solved the problem.
Thanks
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue6
Sébastien Sablé added the comment:
I need Python compiled with Visual Studio 2010 because I use it embedded in an
application compiled with Visual Studio 2010.
I am pretty sure there are quite a lot of people who would like to compile
Python with this compiler.
I have compiled Python 2.7.2
New submission from Sébastien Sablé :
Python for Windows is currently compiled with Visual Studio 2008.
It is not possible to use Visual Studio 2010.
It would be great to be able to compile Python with Visual Studio 2010:
* some people may only have access to this compiler which is more recent
Sébastien Sablé added the comment:
Amaury:
Great! I have opened issue 13210 to achieve that.
Mark:
Mixing the 2 CRTs results in plenty of crashes in our application. The
application also uses a lot of Qt. It is not an option to use a prebuilt Python
binary generated with VS2008.
I added you
Sébastien Sablé added the comment:
Here is a quick and dirty draft of the modifications I had to do in order to
get Python 2.7.2 to compile with VS2010 on the wiki:
http://wiki.python.org/moin/VS2010
I will improve/complete it as I progress.
I will also do a 64 bits version
Sébastien Sablé added the comment:
Martin, what I want to achieve is to ensure that someone can download Python
sources and compile them without any modification using a standard install of
Windows + Visual Studio 2010 SP1.
I don't really care what is the default compiler used to gen
Sébastien Sablé added the comment:
Packaging makes it easier to distribute Python among my colleagues and
customers, so I think it is a nice addition.
OK for the hg clone, I will set up that (I actually already use mercurial
internally to handle those modifications
Sébastien Sablé added the comment:
I can also confirm that this patch corrects the problem with test_asyncore for
Python 2.7 built with VS2010.
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue10
Sébastien Sablé added the comment:
I had the exact same problem when compiling the Python 2.7 branch with Visual
Studio 2010.
In debug mode and 64 bits, python will crash on test_loads_recursion in
test_marshal and on the code provided in msg63536.
Could you please reopen this issue
Sébastien Sablé added the comment:
I don't have the issue anymore when bumping the stack size to 230.
--
___
Python tracker
<http://bugs.python.org/i
Sébastien Sablé added the comment:
I am trying to get Python working when compiled with Visual Studio 2010 (cf
issue 13210).
When running the tests with the python 2.7 branch compiled with VS2010, the
"test_issue_1395_5" in test_io.py will cause Python to eat the whole memory
wi
New submission from Sébastien Sablé :
I am trying to get Python working when compiled with Visual Studio 2010 (cf
issue 13210).
When running the tests with the python 2.7 branch compiled with VS2010, the
"test_issue_1395_5" in test_io.py will cause Python to eat the whole memory
wi
Sébastien Sablé added the comment:
OK, sorry. Done in issue 13461.
--
___
Python tracker
<http://bugs.python.org/issue1395>
___
___
Python-bugs-list mailin
Sébastien Sablé added the comment:
The problem is in CTextIOWrapperTest.test_issue1395_5
Here is the backtrace:
msvcr100d.dll!memset() Line 145Asm
> msvcr100d.dll!_heap_alloc_dbg_impl(unsigned __int64 nSize, int
> nBlockUse, const char * szFileName, int nLin
Sébastien Sablé added the comment:
I don't have commit access on hg.python.org, so I also created a clone on
bitbucket at:
https://bitbucket.org/sablefr/py27vs2010/overview
I work with a patch queue for the moment since everything is not completely
settled yet.
The patch are against p
Sébastien Sablé added the comment:
Yes I know, but this is my primary target as this is the version that I use in
my product for the moment.
I will test python trunk soon now that Python 2.7 with VS2010 is in a rather
good shape.
--
___
Python
Sébastien Sablé added the comment:
Thanks Antoine! It solved the issue.
I will check soon with Python trunk to see if the same thing applies.
--
___
Python tracker
<http://bugs.python.org/issue13
Sébastien Sablé added the comment:
I had the same issue while compiling Python 2.7 with ActivePerl on windows, and
I can confirm that the proposed patch solves the issue.
--
nosy: +sable
versions: +Python 2.7
___
Python tracker
<h
Sébastien Sablé added the comment:
Thanks Terry, I am aware of that.
We are working on making Python work with VS2010 in issue 13210.
I will check with the py3k branch soon and report here if the same problem
applies.
--
___
Python tracker
<h
Sébastien Sablé added the comment:
OK Brian, I checked your clone and I will keep an eye on it.
I have done almost the same thing for the moment. My patch queue includes some
additional corrections for a few more bugs that prevented me from completely
running the test suite (crash dumps).
I
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue11732>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue7833>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sébastien Sablé added the comment:
I have started working on python default branch.
My patch queue is available here:
https://bitbucket.org/sablefr/py3kvs2010/
The result is the following so far:
323 tests OK.
8 tests failed:
test_distutils test_fileio test_gettext test_io test_os
Sébastien Sablé added the comment:
Hi,
sorry for the late reply.
> STINNER Victor added the comment:
>
> At least, I would like to know if Sébastien Sablé (the author of the original
> patch) changed his opinion about this issue since 2007 ;-)
I haven't changed my min
Sébastien Sablé added the comment:
Sorry for the very late reply; I have been quite busy recently with the
birth of my second daughter, a new job, a new home town and soon a new home.
...
> But with your patch, such code wouldn't be thread-safe anymore. This
> patch implies th
Changes by Sébastien Sablé :
Added file: http://bugs.python.org/file22698/patch_dlmalloc_Python_2_7_1.diff
___
Python tracker
<http://bugs.python.org/issue3526>
___
___
Sébastien Sablé added the comment:
> Does it mean the project to have an AIX buildbot is abandoned?
We have a buildbot running internally on AIX. I could not get the necessary
modifications integrated upstream in the official Python buildbot so that we
could plug directly on it.
cf t
Sébastien Sablé added the comment:
I encountered the same problem while compiling the psutil package.
I used Python 3.2.2 that I compiled myself using Visual Studio 2010 SP1 in
Debug mode by following the PCBuild/readme.txt documentation.
I could not compile psutil until I added in setup.py
Sébastien Sablé added the comment:
I used to have the same problem with Python 2.6.5 and AIX 6.1.
Since I updated to Python 2.6.6, the problem does not appear anymore.
So I think it has been corrected between 2.6.5 and 2.6.6.
regards
--
nosy: +sable
Sébastien Sablé added the comment:
Actually, I had the problem with Python 2.6.4 on AIX 6.1, I did not try Python
2.6.5.
But Python 2.6.6 compiles fine on AIX 6.1.
--
___
Python tracker
<http://bugs.python.org/issue8
New submission from Sébastien Sablé :
Hi,
The same problem that was reported in issue 1106262 is appearing again on AIX
6.1 (the following error messages appear sometime when runnning python:
sem_trywait: Permission denied
sem_post: Permission denied
sem_destroy: Permission denied)
It can be
Sébastien Sablé added the comment:
This is also related to issue1234: It was the same issue but concerning AIX
5.2. This patch corrects the problem in the same way but for AIX 6.1.
regards
--
___
Python tracker
<http://bugs.python.org/issue9
Sébastien Sablé added the comment:
The workaround that I have been using is to call configure like this:
./configure --with-gcc=${CC}
(I usually define CC like this: export CC=xlc_r)
Python compiles fine on AIX 6.1 with that.
--
nosy: +sable
Sébastien Sablé added the comment:
Hi,
As reported in this issue and issue 1756343 and issue 1542544, Python does not
produce a shared python library on AIX even with the --enable-shared flag.
I had provided a patch to correct that, but it was breaking static compilation
of Python on AIX
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18688/python266_AIX61_static_gcc_nopatch.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18689/python266_AIX61_static_gcc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18690/python266_AIX61_static_xlc_nopatch.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18691/python266_AIX61_static_xlc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18692/python266_AIX61_shared_gcc_nopatch.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18693/python266_AIX61_shared_gcc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18694/python266_AIX61_shared_xlc_nopatch.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18695/python266_AIX61_shared_xlc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Sébastien Sablé added the comment:
I proposed a patch in issue 941346 to correct this same problem with Python
2.6.6.
regards
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue1756
Sébastien Sablé added the comment:
I proposed a patch in issue 941346 that is different from this one but which
should result in a shared python library on AIX as well.
regards
--
nosy: +sable
___
Python tracker
<http://bugs.python.
Sébastien Sablé added the comment:
Le 01/09/2010 00:16, Antoine Pitrou a écrit :
> In dynamic builds, there seem to be lots of messages such as:
>
> ld: 0711-224 WARNING: Duplicate symbol: .PyLong_FromString
> ld: 0711-224 WARNING: Duplicate symbol: PyLong_FromString
>
> Ar
Sébastien Sablé added the comment:
Hi,
Here is a patch that solves this problem. It was tested with Python 2.6.6 on
AIX 6.1.
The same problem applies to Python 2.7 and 3.x, but since the syntax has been
changed in configure.in for Python 2.7 and 3.x, I need to adapt a little bit my
patch
Sébastien Sablé added the comment:
I can confirm that this problem is still present with Python 3.1.2 on AIX 6.1.
This is just a compilation warning, but the patch in
msg110771 correctly cleans it.
xlc_r -c -DNDEBUG -O -I. -IInclude -I./Include
-I/home/cis/data/bamboo-home-agent-runtime
Sébastien Sablé added the comment:
Hi,
I have updated the patch and adapted it for Python 3.1.2:
* this time ld_so_aix is moved to ld_so_aix.in which is converted to ld_so_aix
by 'configure' so that it has the right version number for the python library
* there are no more wa
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18763/python312_AIX61_static_nopatch.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18764/python312_AIX61_static_patch_shared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18765/python312_AIX61_shared_patch_shared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
--
versions: +Python 2.6, Python 3.1
___
Python tracker
<http://bugs.python.org/issue941346>
___
___
Python-bugs-list mailin
Sébastien Sablé added the comment:
Here is the version of the patch for Python 2.7.
I had to change AC_TRY_COMPILE to AC_COMPILE_IFELSE and AC_TRY_LINK to
AC_LINK_IFELSE.
The syntax in configure.in is the same between Python 2.7 and the trunk. It is
also the same between Python 2.6.6 and
Sébastien Sablé added the comment:
Here is the patch for Python 2.7.
The only difference compared to Python 3.1.2 is that we don't rename
init to PyInit_.
--
versions: +Python 2.6 -Python 3.2
Added file: http://bugs.python.org/file18768/Python-2.7_shared_AIX
Sébastien Sablé added the comment:
Yes Antoine, gcc only handles compilation; the linker is explicitly called
through the ld_so_aix script which handles calling the native ld with the right
flags to import symbols.
I will check with gcc and attach the log on Wednesday (not at work tomorrow
Sébastien Sablé added the comment:
Hum, forget my previous note;I checked ld_so_aix and it actually calls $CC to
handle linking not ld. I suppose gcc will call the native ld.
Anyway, I will run the test with gcc on Wednesday and know for sure if that
works
Sébastien Sablé added the comment:
[rant: grrr, AIX is really a crappy platform; no consistency between releases;
there are dozens of obvious bugs like that... anyway...]
The fact that there is no 64 bits objects in libbsd.a on AIX 6.1 is a
documented bug:
http://www-01.ibm.com/support
Sébastien Sablé added the comment:
Here is a new test for flock. HAVE_FLOCK is defined if we can link a C
application calling flock, or if flock is defined in libbsd.
FLOCK_NEEDS_LIBBSD is also defined in the second case.
AC_MSG_CHECKING(for flock)
have_flock=no
AC_TRY_LINK([
#include
Sébastien Sablé added the comment:
I inverted the actions in the test I proposed in msg115768 (quick note from
home, should have tested at work before posting). It should be:
AC_MSG_CHECKING(for flock)
have_flock=no
AC_TRY_LINK([
#include "confdefs.h"
#include
], [void* p = floc
Sébastien Sablé added the comment:
Here are the build logs for Python 3.1.2 modified with this patch and compiled
with gcc.
The extensions are correctly built.
I also compiled an extension not directly provided in Python source (cx_Oracle)
and it worked fine also.
--
Added file
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18797/python312_AIX61_shared_gcc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
New submission from Sébastien Sablé :
I have the following error when compiling the last rev of branch py3k on an AIX
6 system:
./Modules/makexp_aix Modules/python.exp . libpython3.2.a; xlc_r
-L/home/cis/data/bamboo-home-agent-runtime/xml-data/build-dir/RTAIX30-SUP/target/support/lib
-L
Sébastien Sablé added the comment:
Antoine, I wanted to test this improvement (and others) on the branch py3k (I
was using Python 2.7 and Python 3.1.2 for the moment). But I have some issues
compiling this branch, even without any patch (see issue 9799).
So you may want to wait for the other
Sébastien Sablé added the comment:
For the moment I have:
r73580 = OK
r83318 = OK
r83584 = OK
r83800 = OK
r84000 = ERR
r84522 = ERR
--
___
Python tracker
<http://bugs.python.org/issue9
Sébastien Sablé added the comment:
Bingo, you got it.
r73580 = OK
r83318 = OK
r83584 = OK
r83800 = OK
r83900 = OK
r83950 = OK
r83985 = OK
r83986 = ERR
r84000 = ERR
r84522 = ERR
It was commited by some guy named "antoine.pitrou" ;)
The linker thinks that we have some symbol na
Sébastien Sablé added the comment:
Yes it works if I explicitly specify --without-computed-gotos
--
___
Python tracker
<http://bugs.python.org/issue9799>
___
___
Sébastien Sablé added the comment:
Thanks Michael, your new test looks fine to me.
I wanted to test it on my AIX system with branch py3k but I had some other
issues (issue 9799), but I will test it tomorrow.
--
versions: +Python 2.6, Python 3.3
Sébastien Sablé added the comment:
OK for me to close it as a compiler bug since there is a workaround.
It would be great if we could detect this compiler and deactivate this
optimization automatically, but I am too lazy to search the xlc compiler
documentation for a way to do that.
I
Sébastien Sablé added the comment:
Antoine, I tested this patch on py3k with both gcc and xlc in static and shared
mode and I did not notice any issue.
I attach the build and test logs.
I think you can safely commit it.
--
Added file:
http://bugs.python.org/file18818
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18819/py3k_aix61_static_xlc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18820/py3k_aix61_shared_xlc_pathshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18821/py3k_aix61_static_gcc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18822/py3k_aix61_shared_gcc_patchshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Sébastien Sablé added the comment:
I tested Michael test in msg115868 on my AIX system (AIX 6.1 with flock
correctly present in libbsd) with py3k and it works fine:
checking for flock declaration... yes
checking for flock... no
checking for flock in -lbsd... yes
[103/344] test_fcntl
= OK
I
Changes by Sébastien Sablé :
Removed file:
http://bugs.python.org/file18820/py3k_aix61_shared_xlc_pathshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Changes by Sébastien Sablé :
Added file:
http://bugs.python.org/file18832/py3k_aix61_shared_xlc_pathshared.txt.gz
___
Python tracker
<http://bugs.python.org/issue941
Sébastien Sablé added the comment:
For info: I have no problem compiling _multiprocessing and passing the unittest
test_multiprocessing with py3k rev84631 on AIX 6.1 with xlc_r compiler without
the patch proposed here.
I don't know if this is due to some updates in Python (3.2alpha2+) o
Sébastien Sablé added the comment:
You may want to take a look at issue 941346 in order to compile libpython2.6.so
on AIX.
I also embed python in my AIX application, and I had no problem once python was
compiled as share thanks to the patch provided in the other issue.
--
nosy
Sébastien Sablé added the comment:
For info: I have no problem with test_shutil on AIX 6.1 with python 2.6.6 or
python 3.2alpha2.
There may be no problem anymore.
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue3
Sébastien Sablé added the comment:
Great! Thanks Antoine.
I checked quickly and there is a small correction to do on the 2.7 branch: this
branch is different because there has been a change between python 2.x and 3.x
in pep-3121 concerning the name of the entry function in a module
(init to
Sébastien Sablé added the comment:
Yes, no problem; I will update the Misc/AIX-NOTES file with all the information
I have been collecting recently on Python with AIX.
I will do that when I will have solved some remaining issues I have on AIX, and
also when I will have checked with AIX 5.3 as
Sébastien Sablé added the comment:
cc_r does not seems to be able to compile py3k, so it seems to be a bad idea to
force it by default.
cc_r -qlanglvl=extc89 -DNDEBUG -O -O2 -O2 -I. -IInclude -I./Include
-I/home/cis/buildbot/support-buildbot/include
-I/home/cis/buildbot/support
Sébastien Sablé added the comment:
cc(_r) and xlc(_r) refer to the same binary of the same compiler, but they
change the default configuration of that compiler.
The documentation indicates:
DESCRIPTION
The invocation commands compile C and C++ source files.
The commands
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue7657>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue678250>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue730467>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue713169>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue678264>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue8882>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue5718>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue1745108>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue1563807>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sébastien Sablé added the comment:
Antoine, I tested your commit with cc_r and it compiles fine (I have buildbot
running now, just need to find a way to make the results publicly browsable).
I still think xlc_r would be a better choice as a default: at the moment ctypes
will not compile on
New submission from Sébastien Sablé :
On AIX, the test test_communicate_pipe_buf in test_subprocess will hang forever
(in py3k and py27):
test_communicate_pipe_buf (__main__.ProcessTestCase) ...
File "Lib/test/test_subprocess.py", line 386, in test_communicate_pipe_buf
(stdo
1 - 100 of 205 matches
Mail list logo