This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Michael.Felt
Recipients David.Edelsohn, Michael.Felt, martin.panter, pitrou
Date 2016-03-02.16:42:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1456936961.85.0.366467785691.issue25825@psf.upfronthosting.co.za>
In-reply-to
Content
FYI: when build and src are the same directory, there is no error message. However, when src and build are in seperate directories (e.g.,

build = '.',
src = '../src/python-2.7.11'

the following message occurs MANY times:

unable to execute '../src/python-2.7.11/Modules/ld_so_aix': No such file or directory

during configure the file
./Modules/ld_so_aix is 'created' in the build area.

root@x064:[/data/prj/aixtools/python-2.7.11]ls -l Modules/ld*aix*
-rwxr-xr-x   1 root     system         6205 Mar 02 16:24 Modules/ld_so_aix

Just guessing, but a line such as:
BLDSHARED="\$(srcdir)/Modules/ld_so_aix \$(CC) -bI:\$(srcdir)/Modules/python.exp"

using $(srcdir) is not correct.

Further, a find in $(srcdir) for ld_so_aix returns:
root@x064:[/data/prj/aixtools/python-2.7.11]ls -dl ../src/py*
drwxr-xr-x  17 199      1954           4096 May 23 2015  ../src/python-2.7.10
drwxr-xr-x  17 199      1954           4096 Dec 05 19:47 ../src/python-2.7.11

So, $(srcdir) seems to be wrong, by definition.

For now, I am copying $(srcdir) to $(builddir) to work-around this.
History
Date User Action Args
2016-03-02 16:42:41Michael.Feltsetrecipients: + Michael.Felt, pitrou, martin.panter, David.Edelsohn
2016-03-02 16:42:41Michael.Feltsetmessageid: <1456936961.85.0.366467785691.issue25825@psf.upfronthosting.co.za>
2016-03-02 16:42:41Michael.Feltlinkissue25825 messages
2016-03-02 16:42:41Michael.Feltcreate