Issues compiling 2.6.5 on AIX 6.1
in [Python]
|
From: Thomas Jollans on 8 Jul 2010 12:51 On 07/08/2010 04:36 PM, Stopp, Bryan wrote: > I�ve seen other threads on this issue, but the resolution still doesn�t > seem to exist for me. > > > > I�m running the configure script with these parameters: > > > > ./configure --prefix=/build/tools \ > > --exec-prefix=/build/tools \ > > --enable-shared \ > > --enable-ipv6 \ > > --with-gcc \ > > --with-pth > > > > I also want to state that I already edited all of the configure & > config.guess scripts to comprehend AIX6.1 (they�re not updated yet). This smells horribly like rather risky business. I don't know what you changed or how experienced you are when it comes to editing these auto-generated, system-specific files. Have you tried with Python 2.7, or do you need 2.6? Python 2.7 might work here? Since configure and config.guess are auto-generated, maybe you can regenerate them with a newer/updated version of autoconf that supports your system. Quite frankly, it surprises me that changes to configure would be necessary. Is the system that unusual? What happens if you --disable-shared ? I expect you want the shared library, but - does it work? Just some random thoughts -- I know nothing about AIX and little about cross-UNIX portability beyond, to an extent, GNU vs BSD. Cheers, Thomas
From: Stopp, Bryan on 8 Jul 2010 14:01 These are good points, but I've fixed the configure & config.guess on about 10 other OSS projects that I needed to compile on this machine. So I know that my changes are correct. The changes boil down to: There are a number of lines in the files that reference AIX versions for configuring details about the system. Specifically, it'll be "if" or "case" statements that look like: *-ibm-aix5*) *aix4*|*aix5*) I just add the aix6 clause: *-ibm-aix5* | *-ibm-aix6*) *aix4*|*aix5*|*aix6*) As Aix6 is binary compatible with 5, but the configure defaults it to an unknown AIX version and completely mis-configures the compiler. As for using the autoconf tool for my system, I'm not really sure if it's even installed or if the latest autoconf supports this version. Oddly enough I'm not the sys admin, but I do play one on TV. I do want to stick with Python 2.6 if I can, but I will give compiling 2.7 a shot to see what, if anything, changes/is fixed. Thanks for the feedback! -B -----Original Message----- From: python-list-bounces+cbds=argushealth.com(a)python.org [mailto:python-list-bounces+cbds=argushealth.com(a)python.org] On Behalf Of Thomas Jollans Sent: Thursday, July 08, 2010 11:51 AM To: python-list(a)python.org Subject: Re: Issues compiling 2.6.5 on AIX 6.1 On 07/08/2010 04:36 PM, Stopp, Bryan wrote: > I've seen other threads on this issue, but the resolution still doesn't > seem to exist for me. > > > > I'm running the configure script with these parameters: > > > > ./configure --prefix=/build/tools \ > > --exec-prefix=/build/tools \ > > --enable-shared \ > > --enable-ipv6 \ > > --with-gcc \ > > --with-pth > > > > I also want to state that I already edited all of the configure & > config.guess scripts to comprehend AIX6.1 (they're not updated yet). This smells horribly like rather risky business. I don't know what you changed or how experienced you are when it comes to editing these auto-generated, system-specific files. Have you tried with Python 2.7, or do you need 2.6? Python 2.7 might work here? Since configure and config.guess are auto-generated, maybe you can regenerate them with a newer/updated version of autoconf that supports your system. Quite frankly, it surprises me that changes to configure would be necessary. Is the system that unusual? What happens if you --disable-shared ? I expect you want the shared library, but - does it work? Just some random thoughts -- I know nothing about AIX and little about cross-UNIX portability beyond, to an extent, GNU vs BSD. Cheers, Thomas -- http://mail.python.org/mailman/listinfo/python-list PRIVILEGED AND CONFIDENTIAL This email transmission contains privileged and confidential information intended only for the use of the individual or entity named above. If the reader of the email is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any use, dissemination or copying of this email transmission is strictly prohibited by the sender. If you have received this transmission in error, please delete the email and immediately notify the sender via the email return address or mailto:postmaster(a)argushealth.com. Thank you.
From: Stopp, Bryan on 8 Jul 2010 14:46 I just wanted to follow up my previous email: I tried compiling 2.7 (without editing any config.guess or configure files as they are up to date for AIX6) and it failed with the exact same errors. So I'm still stuck and not sure what I should to do get this to compile. Any other ideas out there? -B -----Original Message----- From: python-list-bounces+cbds=argushealth.com(a)python.org [mailto:python-list-bounces+cbds=argushealth.com(a)python.org] On Behalf Of Thomas Jollans Sent: Thursday, July 08, 2010 11:51 AM To: python-list(a)python.org Subject: Re: Issues compiling 2.6.5 on AIX 6.1 On 07/08/2010 04:36 PM, Stopp, Bryan wrote: > I've seen other threads on this issue, but the resolution still doesn't > seem to exist for me. > > > > I'm running the configure script with these parameters: > > > > ./configure --prefix=/build/tools \ > > --exec-prefix=/build/tools \ > > --enable-shared \ > > --enable-ipv6 \ > > --with-gcc \ > > --with-pth > > > > I also want to state that I already edited all of the configure & > config.guess scripts to comprehend AIX6.1 (they're not updated yet). This smells horribly like rather risky business. I don't know what you changed or how experienced you are when it comes to editing these auto-generated, system-specific files. Have you tried with Python 2.7, or do you need 2.6? Python 2.7 might work here? Since configure and config.guess are auto-generated, maybe you can regenerate them with a newer/updated version of autoconf that supports your system. Quite frankly, it surprises me that changes to configure would be necessary. Is the system that unusual? What happens if you --disable-shared ? I expect you want the shared library, but - does it work? Just some random thoughts -- I know nothing about AIX and little about cross-UNIX portability beyond, to an extent, GNU vs BSD. Cheers, Thomas -- http://mail.python.org/mailman/listinfo/python-list PRIVILEGED AND CONFIDENTIAL This email transmission contains privileged and confidential information intended only for the use of the individual or entity named above. If the reader of the email is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any use, dissemination or copying of this email transmission is strictly prohibited by the sender. If you have received this transmission in error, please delete the email and immediately notify the sender via the email return address or mailto:postmaster(a)argushealth.com. Thank you.
From: Thomas Jollans on 9 Jul 2010 08:10 On 07/08/2010 04:36 PM, Stopp, Bryan wrote: > building '_struct' extension > > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall > -Wstrict-prototypes -I. -I/build/tools/src/Python-2.6.5/./Include > -I/build/tools/include -I. -IInclude -I./Include -I/usr/local/include > -I/build/tools/src/Python-2.6.5/Include -I/build/tools/src/Python-2.6.5 > -c /build/tools/src/Python-2.6.5/Modules/_struct.c -o > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > > ./Modules/ld_so_aix gcc -pthread -bI:Modules/python.exp > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > -L/build/tools/lib -L/usr/local/lib -lpython2.6 -o > build/lib.aix-6.1-2.6/_struct.so > > collect2: library libpython2.6 not found What really stumps me (and you too, I expect) about this is the two different error messages. Above, it looks like collect2 simply doesn't find a -lpython2.6 anywhere. Adding . to LIBPATH does make sense. > building '_struct' extension > > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall > -Wstrict-prototypes -I. -I/build/tools/src/Python-2.6.5/./Include > -I/build/tools/include -I. -IInclude -I./Include -I/usr/local/include > -I/build/tools/src/Python-2.6.5/Include -I/build/tools/src/Python-2.6.5 > -c /build/tools/src/Python-2.6.5/Modules/_struct.c -o > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > > ./Modules/ld_so_aix gcc -pthread -bI:Modules/python.exp > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > -L/build/tools/lib -L/usr/local/lib -lpython2.6 -o > build/lib.aix-6.1-2.6/_struct.so > > ld: 0706-006 Cannot find or open library file: -l python2.6 > > ld:open(): No such file or directory > > collect2: ld returned 255 exit status But what on earth is this? It looks like collect2 found the library, and told it's mate ld, which can't open it. collect2 thinks it find a file, ld hits "No such file or directory" on the same file. Maybe it's a dead symlink? Looking for a file with the right name and location would find it, while opening it would hit a dead end, and probably return "No such file "
From: Stopp, Bryan on 9 Jul 2010 08:54 I checked, none of the files are symlinks. The install process never got to the point where it created sym-links for libraries (if it even does, I haven't gotten to that point in the install process.) -B -----Original Message----- From: python-list-bounces+cbds=argushealth.com(a)python.org [mailto:python-list-bounces+cbds=argushealth.com(a)python.org] On Behalf Of Thomas Jollans Sent: Friday, July 09, 2010 7:10 AM To: python-list(a)python.org Subject: Re: Issues compiling 2.6.5 on AIX 6.1 On 07/08/2010 04:36 PM, Stopp, Bryan wrote: > building '_struct' extension > > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall > -Wstrict-prototypes -I. -I/build/tools/src/Python-2.6.5/./Include > -I/build/tools/include -I. -IInclude -I./Include -I/usr/local/include > -I/build/tools/src/Python-2.6.5/Include -I/build/tools/src/Python-2.6.5 > -c /build/tools/src/Python-2.6.5/Modules/_struct.c -o > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > > ./Modules/ld_so_aix gcc -pthread -bI:Modules/python.exp > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > -L/build/tools/lib -L/usr/local/lib -lpython2.6 -o > build/lib.aix-6.1-2.6/_struct.so > > collect2: library libpython2.6 not found What really stumps me (and you too, I expect) about this is the two different error messages. Above, it looks like collect2 simply doesn't find a -lpython2.6 anywhere. Adding . to LIBPATH does make sense. > building '_struct' extension > > gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall > -Wstrict-prototypes -I. -I/build/tools/src/Python-2.6.5/./Include > -I/build/tools/include -I. -IInclude -I./Include -I/usr/local/include > -I/build/tools/src/Python-2.6.5/Include -I/build/tools/src/Python-2.6.5 > -c /build/tools/src/Python-2.6.5/Modules/_struct.c -o > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > > ./Modules/ld_so_aix gcc -pthread -bI:Modules/python.exp > build/temp.aix-6.1-2.6/build/tools/src/Python-2.6.5/Modules/_struct.o > -L/build/tools/lib -L/usr/local/lib -lpython2.6 -o > build/lib.aix-6.1-2.6/_struct.so > > ld: 0706-006 Cannot find or open library file: -l python2.6 > > ld:open(): No such file or directory > > collect2: ld returned 255 exit status But what on earth is this? It looks like collect2 found the library, and told it's mate ld, which can't open it. collect2 thinks it find a file, ld hits "No such file or directory" on the same file. Maybe it's a dead symlink? Looking for a file with the right name and location would find it, while opening it would hit a dead end, and probably return "No such file " -- http://mail.python.org/mailman/listinfo/python-list PRIVILEGED AND CONFIDENTIAL This email transmission contains privileged and confidential information intended only for the use of the individual or entity named above. If the reader of the email is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any use, dissemination or copying of this email transmission is strictly prohibited by the sender. If you have received this transmission in error, please delete the email and immediately notify the sender via the email return address or mailto:postmaster(a)argushealth.com. Thank you.
|
Pages: 1 Prev: How is Unladen Swallow coming along? Next: ANN: ActivePython 2.6.5.14 is now available |