Problems building numpy
from numpy import array import linalg -> failed: /usr/local/lib/python2.4/site-packages/numpy/
Numpy really builds nicely now, and I appreciate all of the hard work that people have put into portability of this code. That being said, I just had my first system where Numpy failed to build. It's on a redhat 7.3 (yes, we have a 7.3 box. I didn't believe it either. not my decision.) and I get the following error when trying to run Numpy: Python 2.4.3 (#1, Apr 24 2006, 09:54:46) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-42)] on linux2 Type "help", "copyright", "credits" or "license" for more information. linalg/lapack_lite.so: undefined symbol: s_wsfe If this is easy to fix, I'd prefer to fix it. However, if the numpy developers have better things to do than to support a 10-year-old operating system (and I suspect that they do), I'm cool with that. Rick Rick Muller rmuller@sandia.gov
Rick Muller wrote:
Numpy really builds nicely now, and I appreciate all of the hard work that people have put into portability of this code.
That being said, I just had my first system where Numpy failed to build. It's on a redhat 7.3 (yes, we have a 7.3 box. I didn't believe it either. not my decision.) and I get the following error when trying to run Numpy:
from numpy import array import linalg -> failed: /usr/local/lib/python2.4/site-packages/numpy/
Python 2.4.3 (#1, Apr 24 2006, 09:54:46) [GCC 3.2.3 20030502 (Red Hat Linux 3.2.3-42)] on linux2 Type "help", "copyright", "credits" or "license" for more information. linalg/lapack_lite.so: undefined symbol: s_wsfe
If this is easy to fix, I'd prefer to fix it. However, if the numpy developers have better things to do than to support a 10-year-old operating system (and I suspect that they do), I'm cool with that.
This usually means that you are not linking in the g2c library: http://www.scipy.org/FAQ#head-26562f0a9e046b53eae17de300fc06408f9c91a8 -- Robert Kern robert.kern@gmail.com "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
Robert Kern wrote:
Rick Muller wrote:
That being said, I just had my first system where Numpy failed to build. It's on a redhat 7.3 (yes, we have a 7.3 box. I didn't believe it either. not my decision.) and I get the following error when trying to run Numpy:
This usually means that you are not linking in the g2c library.
On Redhat 7.3, I don't believe there was a g2c library, but an f2c one. So -lf2c is needed at the link step (and f2c needs to be installed).
Stephen Walton wrote:
Robert Kern wrote:
Rick Muller wrote:
That being said, I just had my first system where Numpy failed to build. It's on a redhat 7.3 (yes, we have a 7.3 box. I didn't believe it either. not my decision.) and I get the following error when trying to run Numpy:
This usually means that you are not linking in the g2c library.
On Redhat 7.3, I don't believe there was a g2c library, but an f2c one. So -lf2c is needed at the link step (and f2c needs to be installed).
Well, there's libf2c which is a library provided by f2c, a program that converts FORTRAN to C. And then there's libg2c which is provided by g77. They really are different and, I don't think, interchangeable. Note that libg2c will be stuck several ellipses down in the bowels of /usr/lib/gcc/.../.../libg2c.a not up in /usr/lib/. -- Robert Kern robert.kern@gmail.com "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
Robert Kern wrote:
Well, there's libf2c which is a library provided by f2c, a program that converts FORTRAN to C. And then there's libg2c which is provided by g77. They really are different
Oh, I knew that. My point was that there were some old Redhat releases (I don't recall if 7.3 is that old, probably not) which didn't include g77, just an f77 shell script which called f2c and cc.
Stephen Walton wrote:
Robert Kern wrote:
Well, there's libf2c which is a library provided by f2c, a program that converts FORTRAN to C. And then there's libg2c which is provided by g77. They really are different
Oh, I knew that. My point was that there were some old Redhat releases (I don't recall if 7.3 is that old, probably not) which didn't include g77, just an f77 shell script which called f2c and cc.
Oy. I'm not sure if even we support that. -- Robert Kern robert.kern@gmail.com "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephen Walton wrote: | Robert Kern wrote: | |> Well, there's libf2c which is a library provided by f2c, a program |> that converts |> FORTRAN to C. And then there's libg2c which is provided by g77. They |> really are |> different | | Oh, I knew that. My point was that there were some old Redhat releases | (I don't recall if 7.3 is that old, probably not) which didn't include | g77, just an f77 shell script which called f2c and cc. And in addition, very old versions of g77 (I'm not sure to which RedHat version this age corresponds) used f2c's library unmodified. I think the f2c/cc times (the compiler script was called fcomp?) were a bit older. I moved back to my current job with RedHat 4.x (1997), and I worked with self-compiled g77 already in my previous job.... Rob - -- Rob W.W. Hooft || rob@hooft.net || http://www.hooft.net/people/rob/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFETaRzH7J/Cv8rb3QRAqtEAKCsDcj3tO7Gcvgsyj0CaDCu99JLSgCgjgjp sB7u8S0krk5a1G2bYC+h9cQ= =MLOS -----END PGP SIGNATURE-----
participants (4)
-
Rick Muller -
Rob Hooft -
Robert Kern -
Stephen Walton