54 lines
2.0 KiB
Plaintext
54 lines
2.0 KiB
Plaintext
From: olipt at mayo.edu (Travis Oliphant)
|
|
Date: Sun, 25 Apr 1999 20:03:12 -0500
|
|
Subject: HELP! NumPy (Graphics) and Linux
|
|
In-Reply-To: <7fvpsh$l8e$1@nnrp1.dejanews.com>
|
|
References: <7fvpsh$l8e$1@nnrp1.dejanews.com>
|
|
Message-ID: <Pine.LNX.4.04.9904251950250.28850-100000@us2.mayo.edu>
|
|
Content-Length: 1688
|
|
X-UID: 378
|
|
|
|
Glad to hear that you are using NumPy on Linux.
|
|
|
|
I've been putting together the RPM's for NumPy and would definitely
|
|
suggest you go that route initially. If you want to compile the packages
|
|
yourself you can get the source RPM for Numpy from andrich.net or from my
|
|
site at http://oliphant.netpedia.net and it will build 3 binary packages:
|
|
NumPy, Gist (EzPlot), and RNG (random number generators). The packages
|
|
come with quite a bit of documentation (all I could find).
|
|
|
|
Installing a source RPM and then compiling amounts to:
|
|
|
|
rpm -i package-name.src.rpm
|
|
rpm -ba /usr/src/redhat/SPECS/package.spec
|
|
|
|
This will build a binary package compiled on your system and place it in
|
|
/usr/src/redhat/RPMS/i386
|
|
|
|
You can then install it like any other package.
|
|
|
|
I would highly encourage learning to build from RPM sources. Grabbing a
|
|
spec file is usually all you need to start building any package you want.
|
|
If you stick with Oliver's RPM's you should be fine. I've had trouble in
|
|
the past however with compiling my own RPM's (using gcc) and trying to
|
|
import them into a python interpreter installed from Oliver's RPMS
|
|
(compiled with pgcc). I get strange segfaults. I haven't tried for
|
|
awhile so I don't know if the problem is still there but you might keep
|
|
that in mind if you are mixing and matching compilers for different python
|
|
packages.
|
|
|
|
After that bit of rambling... The problem you are having is due to the
|
|
fact that the gist module now looks for the arrayobject.h file in
|
|
numerical/arrayobject.h which is not where your arrayobject.h header file
|
|
likely is. So, change that #include line in the C-code and it should
|
|
work. I had to do this to get the RPM's to work.
|
|
|
|
Best,
|
|
|
|
Travis
|
|
|
|
|
|
|
|
|
|
|
|
|