Sébastien Sablé sa...@users.sourceforge.net added the comment:
There are some unit tests concerning distutils which are currently failing on
AIX and may be an illustration of the same problem:
==
ERROR: test_build_ext
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Yes I will do that.
I am currently reinstalling some buildbot environments for Python on AIX 5.3
and AIX 6.1 and once that is done, I will rewrite the note.
--
___
Python tracker rep
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Hi Micheal,
I don't remember why -L\$(srcdir) was added since it has been quite a long
time.
I tried to recompile everything after removing it and everything compiled just
fine, so I guess it can be removed.
regards
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is a patch that combines the corrections in configure.in and dynload_aix.c.
All recent versions of AIX would benefit from this correction I think (recent
meaning a version of AIX released in the last 10 years or something
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Mark,
sorry for the late reply; I stopped focusing on AIX for some time.
I ran test_cmath on trunk this morning and got a different error this time:
==
FAIL
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I tried with trunk (python 3.2) on AIX:
./build/configure --with-pydebug --without-computed-gotos
make
and that worked correctly.
Not sure with python 2.7.
--
___
Python tracker rep
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I get 2 errors when running test_io.py with trunk on AIX.
==
ERROR: test_large_file_ops (__main__.CIOTest
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I get an error when running test_wait4 with trunk on AIX:
test_wait (__main__.Wait4Test) ... FAIL
==
FAIL: test_wait (__main__.Wait4Test
Sébastien Sablé sa...@users.sourceforge.net added the comment:
OK, so the following patch should help:
Index: configure.in
===
--- configure.in(revision 88393)
+++ configure.in(working copy)
@@ -1375,6 +1375,8
Sébastien Sablé sa...@users.sourceforge.net added the comment:
the error is different now that _LARGEFILES is defined:
==
ERROR: test_large_file_ops (__main__.CIOTest
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Sorry I made a mistake in my previous patch (_LARGEFILES instead of
_LARGE_FILES).
Here is a better one:
Index: configure.in
===
--- configure.in(révision
Sébastien Sablé sa...@users.sourceforge.net added the comment:
test_largefile complains about the filesystem having no largefile support.
It is probably the case, I will ask a sysadmin, and see if he can get me a file
system with large file support so that I can test this feature.
./python
Changes by Sébastien Sablé sa...@users.sourceforge.net:
--
title: test_io error on AIX - Broken large file support on AIX
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11184
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Also:
is it OK if I open a new issue for each broken unit test on AIX even if I have
not investigated them at the moment?
I have a dozen broken unit tests on AIX that need to be investigated, but I
don't want to spam the bug
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following errors on test_time on AIX:
==
ERROR: test_mktime (test.test_time.TestAsctime4dyear
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following error on test_resource on AIX:
test_resource
test test_resource failed -- Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_resource.py
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following errors on test_locale on AIX:
==
FAIL: test_strcoll_with_diacritic (test.test_locale.TestEnUSCollation
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following error in distutils on AIX.
==
ERROR: test_search_cpp (distutils.tests.test_config_cmd.ConfigTestCase
Changes by Sébastien Sablé sa...@users.sourceforge.net:
--
title: test_search_cpp error on AIX (aith xlc) - test_search_cpp error on AIX
(with xlc)
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11191
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following error in test_socket on AIX:
==
FAIL: testGetaddrinfo (__main__.GeneralModuleTests
Sébastien Sablé sa...@users.sourceforge.net added the comment:
This is a duplicate of issue 678264.
--
resolution: - duplicate
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11189
New submission from Sébastien Sablé sa...@users.sourceforge.net:
The following tests fail in test_subprocess on AIX:
==
FAIL: test_undecodable_env (test.test_subprocess.POSIXProcessTestCase
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I am not sure this is what you want:
LC_ALL=C ./python
Python 3.2rc3 (py3k:88417M, Feb 14 2011, 10:37:42)
[GCC 4.2.0] on aix6
Type help, copyright, credits or license for more information.
import sys
sys.getfilesystemencoding
New submission from Sébastien Sablé sa...@users.sourceforge.net:
On AIX, executables are compiled by default so that they cannot allocate more
than 256MB of memory.
This is not enough in some cases; for example this is not enough to get the
Python test suite to run completely.
As explained
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is a patch that would provide an --enable-aix-maxdata option to configure,
in order to support 512MB of mermory.
I have not tested it yet.
--
keywords: +patch
Added file: http://bugs.python.org/file20761
Sébastien Sablé sa...@users.sourceforge.net added the comment:
$ LANG=C ./python -Wd -E -bb -c import sys; print(ascii(sys.argv)) $(echo -ne
abc\xff)['-c', 'abc\xff']
['-c', 'abc\xff']
$ LANG=C ./python -Wd -E -bb -c import locale;
print(locale.nl_langinfo(locale.CODESET))
ISO8859-1
$ LANG=C
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I tried the following patch (_AIX is defined on AIX platforms):
Index: Modules/timemodule.c
===
--- Modules/timemodule.c(révision 88420)
+++ Modules
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is the result after applying that patch:
==
FAIL: test_specific_values (__main__.CMathTests
New submission from Sébastien Sablé sa...@users.sourceforge.net:
When running test_asyncore on AIX, I get the following error:
[122/337] test_asyncore
test test_asyncore failed -- Traceback (most recent call last):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test
New submission from Sébastien Sablé sa...@users.sourceforge.net:
I have the following error when running test_fileio on AIX:
==
FAIL: testAbles (test.test_fileio.OtherFileTests
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Yes, welcome into the strange world of AIX...
You can allow up to 8 segments, which represent 2GB:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame3.doc_5.1/am51_perftune113.htm
We could change
Sébastien Sablé sa...@users.sourceforge.net added the comment:
If have the same issue with Oracle Studio 12.2 on Solaris 10 with Python 2.7.1:
cc -G -L/livraison/test/sparc-sun-solaris2.10/support/support-2.6.x-py27/lib
-L/livraison/test/sparc-sun-solaris2.10/support/support-internal-2.6
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Hum, I was incorrect in previous note:
You can remove -L\$(srcdir) on this line, but then you need to specify the full
path to Modules/python.exp. See patch below:
Index: configure.in
Sébastien Sablé sa...@users.sourceforge.net added the comment:
OK, Python with shared libraries is broken in trunk since the library was
renamed to libpython3.2m.
Here is a patch to correct that:
Index: Modules/ld_so_aix.in
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is the full patch.
I also modified Makefile.pre.in to clean Modules/python.exp when doing
distclean.
--
Added file: http://bugs.python.org/file20764/patch_aix_shared_32.diff
Sébastien Sablé sa...@users.sourceforge.net added the comment:
This link flag should only be applied to the python executable.
There is already LINKFORSHARED which is great for that.
LDFLAGS will apply it to all the shared libraries which is not really what we
want.
I can compile Python
Changes by Sébastien Sablé sa...@users.sourceforge.net:
--
versions: +Python 2.6, Python 2.7, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11212
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I don't know distutils well enough, but I am afraid the LDFLAGS flag used to
compile python is reused in some way when linking some python extensions or
some application that embed python.
(I use an application that embed python
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is what I could find in the man mktime:
Upon successful completion, the mktime subroutine sets the values of the
tm_wday and tm_yday fields appropriately. Other fields are set to
represent the specified time
Sébastien Sablé sa...@users.sourceforge.net added the comment:
This bug is still present in Python 2.7.1. I have also just been beaten by it
on solaris.
I have libintl.so.1 in /usr/lib and libintl.so.8 in /usr/local/lib.
I have never specified that I wanted to use /usr/local/lib anywhere
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I can only bypass this by explicitly specifying -L/usr/lib so that it will take
precedence over -L/usr/local/lib.
But this behavior is still broken...
Explicit is better than implicit.
I can see no reason why /usr/local should
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Python 3.2rc3+ (py3k:88422M, Feb 15 2011, 16:57:29) [C] on aix6
Type help, copyright, credits or license for more information.
import time
for t in (-2, -1, 0, 1):
... print(time.localtime(t))
...
time.struct_time(tm_year=1970
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Antoine,
can you take a look at issue 730467? That's a trivial patch to correct a
compilation issue on AIX with a C++ compiler; and that means one less entry in
the AIX-NOTES file to write before the 3.2 release
Sébastien Sablé sa...@users.sourceforge.net added the comment:
gmtime(-1) worked fine :/
import time
time.gmtime(-1)
time.struct_time(tm_year=1969, tm_mon=12, tm_mday=31, tm_hour=23, tm_min=59,
tm_sec=59, tm_wday=2, tm_yday=365, tm_isdst=0
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Are you using --enable-shared when compiling python?
That is when you should see the error (it could not find python.exp at some
stage).
--
___
Python tracker rep...@bugs.python.org
http
Sébastien Sablé sa...@users.sourceforge.net added the comment:
By the way... thanks Georg!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Also Michael, I am working on the 3.2 branch, it may be different with Python
2.7.1 but I haven't tested yet.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is the patch.
It only impacts AIX systems and is minimalist, so I think it should be safe for
Python 3.2.
--
keywords: +patch
Added file: http://bugs.python.org/file20767/patch_aix_largefile.diff
Sébastien Sablé sa...@users.sourceforge.net added the comment:
This has been corrected for python 3.2 in issue 941346.
Need to be tested on python 2.7.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11172
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is a first version of this doc for Python 3.2.
It would be great if someone could proof read it since I am not a native
english speaker (though it is not high level literature...).
--
Added file: http://bugs.python.org
New submission from Sébastien Sablé sa...@users.sourceforge.net:
The test test_lock_acquire_interruption in test_threadsignals.py will lock
forever on AIX 5.3.
It works fine on 6.1.
truss shows it is stuck in thread_tsleep:
$ truss -p 1404986
thread_tsleep(0, 0x, 0x, 0x
Sébastien Sablé sa...@users.sourceforge.net added the comment:
$ grep SEM pyconfig.h
#define HAVE_BROKEN_POSIX_SEMAPHORES 1
/* #undef HAVE_BROKEN_SEM_GETVALUE */
#define HAVE_SEM_GETVALUE 1
#define HAVE_SEM_OPEN 1
#define HAVE_SEM_TIMEDWAIT 1
#define HAVE_SEM_UNLINK 1
/* #undef
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I am not sure this is directly related, but test_socket.py will hang forever on
AIX 6.1 when this script is run as part of make buildbottest.
It won't hang when running the script alone
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Thanks Antoine, the patch solved the problem.
I have other tests locking semi-randomly on AIX 5.3 and/or AIX 6.1, like
test_socket and test_io. That may be related.
--
___
Python
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Well I don't know precisely:
* when running make buildbottest, test_socket will systematically hang on AIX
5.3 and 6.1.
* but when running ./python -Wd -E -bb Lib/test/test_socket.py, the tests
complete rather quickly (with one
Sébastien Sablé sa...@users.sourceforge.net added the comment:
test_socket didnot lock this time (I will retry next).
But test_subprocess.ProcessTestCasePOSIXPurePython.test_leaking_fds_on_error
did.
Looping forever on the following syscall:
pipe(0x2FF1FD88
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is what faulthandler reports when I trigger it as Python is locked in
test_socket:
[108/349] test_socket
Traceback (most recent call first):
File
/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test
Sébastien Sablé sa...@users.sourceforge.net added the comment:
faulthandler is great by the way! I will use that in my application.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11223
Sébastien Sablé sa...@users.sourceforge.net added the comment:
At the time of the lock, there is only one python process running. So I guess
the other processes have already left but this is not correctly detected.
I will try again with all_threads=True
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I kinda feel this is related to issue 11185 which I reported earlier.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11223
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Could this doc be added before the 3.2 release?
I think it is convenient for the (few) AIX users and harmless.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Sébastien Sablé sa...@users.sourceforge.net added the comment:
This issue already existed on Python 2.5.2 with AIX 5.2:
http://www.mail-archive.com/python-list@python.org/msg192219.html
The documentation for WNOHANG says:
http://docs.python.org/library/os.html#os.WNOHANG
The option
Sébastien Sablé sa...@users.sourceforge.net added the comment:
The AIX documentation says:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame3.doc_5.1/am51_perftune113.htm
It is a good idea to unset the LDR_CNTRL environment variable, so that it
does
Sébastien Sablé sa...@users.sourceforge.net added the comment:
The doc would become:
To allocate more segment registers to Python, you must use the linker option
-bmaxdata or ldedit to specify the number of bytes you need in the data
segment.
For example, if you want to allow 512MB
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Yes it is correct. And thank you for proof reading it too.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10709
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Here is a new version of the file:
It integrates the corrections by R. David, and I also modified the memory
limitations section in order to use ldedit rather than some flags for the
linker.
--
Added file: http
Sébastien Sablé sa...@users.sourceforge.net added the comment:
I updated the documentation in issue 10709 so that it mentions ldedit rather
than the linker flags (more convenient to activate support for more memory).
Once Python 3.2 is released, we may add LDR_CNTRL or ldedit in the Makefile
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Great!
I intend to check that branch 2.7 works fine on AIX once I will have finished
with 3.x (which should be soon).
I will then update this file for Python 2.7 (there shouldn't be much changes
hopefully
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-June
Changes by
Sébastien Sablé
:
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1234
__
___
Python-bugs-list
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/issue1234
Sébastien Sablé sa...@users.sourceforge.net added the comment:
Well I am still interested in getting this patch officially integrated in
Python.
This patch is integrated in the version of Python that we deploy to our
customers with our products (Sungard GP3). So it runs in production
Sébastien Sablé sa...@users.sourceforge.net 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é sa...@users.sourceforge.net 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 rep...@bugs.python.org
http
New submission from Sébastien Sablé sa...@users.sourceforge.net:
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
Sébastien Sablé sa...@users.sourceforge.net 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 rep
Sébastien Sablé sa...@users.sourceforge.net 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é sa...@users.sourceforge.net 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
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18688/python266_AIX61_static_gcc_nopatch.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18689/python266_AIX61_static_gcc_patchshared.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18690/python266_AIX61_static_xlc_nopatch.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18691/python266_AIX61_static_xlc_patchshared.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18692/python266_AIX61_shared_gcc_nopatch.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18693/python266_AIX61_shared_gcc_patchshared.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18694/python266_AIX61_shared_xlc_nopatch.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18695/python266_AIX61_shared_xlc_patchshared.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Sébastien Sablé sa...@users.sourceforge.net 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 rep...@bugs.python.org
http://bugs.python.org/issue1756343
Sébastien Sablé sa...@users.sourceforge.net 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 rep
Sébastien Sablé sa...@users.sourceforge.net 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
Sébastien Sablé sa...@users.sourceforge.net 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
Sébastien Sablé sa...@users.sourceforge.net 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
Sébastien Sablé sa...@users.sourceforge.net 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
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18763/python312_AIX61_static_nopatch.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18764/python312_AIX61_static_patch_shared.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
Added file:
http://bugs.python.org/file18765/python312_AIX61_shared_patch_shared.txt.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Changes by Sébastien Sablé sa...@users.sourceforge.net:
--
versions: +Python 2.6, Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue941346
Sébastien Sablé sa...@users.sourceforge.net 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
Sébastien Sablé sa...@users.sourceforge.net 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
initmodulname to PyInit_modulename.
--
versions: +Python 2.6 -Python 3.2
Added file: http://bugs.python.org/file18768
1 - 100 of 200 matches
Mail list logo
