Compiling Python 2.5.2 on AIX 5.2

[Randy Galbraith]

On Apr 22, 11:17 am, "Martin v. Löwis" <mar... at v.loewis.de> wrote:
> > test test_mmap crashed -- <type 'exceptions.EnvironmentError'>: [Errno
> > 22] Invalid argument
>
> You should run this with -v. This is too little detail to know what
> exactly failed.

Sorry it took so long to get back to you.  At this point, I'm going to
attempt to use python on AIX 5.2 even with the mmap and wait4
failures.  My main requirement running Mercurial SCM, so hopefully the
python binary I have will do the job.

Nonetheless, I wanted to quickly dump out the expanded results you
suggested might help.

Running this:
./python Lib/test/test_mmap.py -v

Resulted in this:
--results--
<type 'mmap.mmap'>
  Position of foo: 1.0 pages
  Length of file: 2.0 pages
  Contents of byte 0: '\x00'
  Contents of first 3 bytes: '\x00\x00\x00'

  Modifying file's content...
  Contents of byte 0: '3'
  Contents of first 3 bytes: '3\x00\x00'
  Contents of second page: '\x00foobar\x00'
  Regex match on mmap (page start, length of match): 1.0 6
  Seek to zeroth byte
  Seek to 42nd byte
  Seek to last byte
  Try to seek to negative position...
  Try to seek beyond end of mmap...
  Try to seek to negative position...
  Attempting resize()
  Creating 10 byte test data file.
  Opening mmap with access=ACCESS_READ
  Ensuring that readonly mmap can't be slice assigned.
  Ensuring that readonly mmap can't be item assigned.
  Ensuring that readonly mmap can't be write() to.
  Ensuring that readonly mmap can't be write_byte() to.
  Ensuring that readonly mmap can't be resized.
  Opening mmap with size too big
  Opening mmap with access=ACCESS_WRITE
  Modifying write-through memory map.
  Opening mmap with access=ACCESS_COPY
  Modifying copy-on-write memory map.
Traceback (most recent call last):
  File "Lib/test/test_mmap.py", line 393, in <module>
    test_both()
  File "Lib/test/test_mmap.py", line 247, in test_both
    m.flush()
EnvironmentError: [Errno 22] Invalid argument
--end results--

btw I'm not sure if -v was required in this direct run.  Running w/o -
v gave the same results.

Now, over to wait4.  Your comment was:

> That suggests a bug in wait4: apparently, it fails to correctly return
> the PID. Could be an OS bug, but more likely, it's a type problem in
> Modules/posixmodule.c.

Running this:
./python Lib/test/test_wait4.py

Resulted in this:
--results--
test_wait (__main__.Wait4Test) ... FAIL

======================================================================
FAIL: test_wait (__main__.Wait4Test)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/..<snip>../Python-2.5.2/Lib/test/fork_wait.py", line 75, in
test_wait
    self.wait_impl(cpid)
  File "Lib/test/test_wait4.py", line 28, in wait_impl
    self.assertEqual(spid, cpid)
AssertionError: 0 != 8417358

----------------------------------------------------------------------
Ran 1 test in 12.066s

FAILED (failures=1)
Traceback (most recent call last):
  File "Lib/test/test_wait4.py", line 37, in <module>
    test_main()
  File "Lib/test/test_wait4.py", line 33, in test_main
    run_unittest(Wait4Test)
  File "/..<snip>../Python-2.5.2/Lib/test/test_support.py", line 451,
in run_unittest
    run_suite(suite, testclass)
  File "/..<snip>../Python-2.5.2/Lib/test/test_support.py", line 436,
in run_suite
    raise TestFailed(err)
test.test_support.TestFailed: Traceback (most recent call last):
  File "/..<snip>../Python-2.5.2/Lib/test/fork_wait.py", line 75, in
test_wait
    self.wait_impl(cpid)
  File "Lib/test/test_wait4.py", line 28, in wait_impl
    self.assertEqual(spid, cpid)
AssertionError: 0 != 8417358
--end results--

Thanks for taking your time to respond.  It is truly appreciated at
this end.

Kind regards,
-Randy Galbraith