By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,525 Members | 1,623 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,525 IT Pros & Developers. It's quick & easy.

compiling python 2.4.1 on Linux_X86_64 using PGI compiler fails

P: n/a

I am trying to compile Python on an Opteron machine using the PGI C
compiler under Linux. I use:

CC=pgcc ./configure --prefix=/usr/local/gltools/python/Python-2.2.1 \
--exec-prefix=/usr/local/gltools/python/Python-2.2.1/$GL_ARCH \
--with-cxx=pgCC

but make fails with:

pgCC -Xlinker -export-dynamic -o python \
Modules/ccpython.o \
libpython2.4.a -lpthread -ldl -lpthread -lutil -lm
libpython2.4.a(posixmodule.o)(.text+0x38d6): In function `posix_tmpnam':
: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp'
libpython2.4.a(posixmodule.o)(.text+0x3841): In function `posix_tempnam':
: warning: the use of `tempnam' is dangerous, better use `mkstemp'
case $MAKEFLAGS in \
*-s*) CC='pgcc' LDSHARED='pgcc -shared' OPT='-DNDEBUG -O' ./python -E ./setup.py -q build;; \
*) CC='pgcc' LDSHARED='pgcc -shared' OPT='-DNDEBUG -O' ./python -E ./setup.py build;; \
esac
make: *** [sharedmods] Error 139

and issuing the last command from the command line gives:
CC='pgcc' LDSHARED='pgcc -shared' OPT='-DNDEBUG -O' ./python -E ./setup.py build

Segmentation fault (core dumped)

This is with PGI 5.2 and 6.0.

Has anyone compiled python successfully using PGI compilers under 64
bit Linux. If yes, what are the neccesarry switches?

Thanks
Berthold
--
ho**@GL-Group.com __ Address:
G / \ L Germanischer Lloyd
phone: +49-40-36149-7374 -+----+- Vorsetzen 35 P.O.Box 111606
fax : +49-40-36149-7320 \__/ D-20459 Hamburg D-20416 Hamburg
Jul 19 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Berthold Höllmann wrote:
Has anyone compiled python successfully using PGI compilers under 64
bit Linux. If yes, what are the neccesarry switches?


As a starting point, I would try to compile without optimization.

If the compiler has something similar to gcc's -fno-strict-aliasing,
you should pass that as well.

Regards,
Martin
Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.