The default section of the code compiled just fine and the FFT is
working great. Thanks so much for your help!
-Dave
Travis Oliphant wrote:
> David Shepherd wrote:
>> My message may have gotten lost over the weekend, but I wanted to see if
>> anyone had anything else I can try to fix the probl
Well, we only need to do an FFT. So I will try all your suggestions
tonight and let you know of the results. Thanks for your help!
-Dave
Travis Oliphant wrote:
> David Shepherd wrote:
>> My message may have gotten lost over the weekend, but I wanted to see if
>> anyone had anything else I can
David Shepherd wrote:
> My message may have gotten lost over the weekend, but I wanted to see if
> anyone had anything else I can try to fix the problem. We have to demo
> this project for a ECE project on Thursday and I was hoping to get the
> FFT working.
>
I know nothing about ulibc. D
David Shepherd wrote:
> My message may have gotten lost over the weekend, but I wanted to see if
> anyone had anything else I can try to fix the problem. We have to demo
> this project for a ECE project on Thursday and I was hoping to get the
> FFT working.
>
>
Ideally, you can help us get
] Numpy with uclibc compiled python
Date: Fri, 06 Apr 2007 16:02:51 -0400
From: David Shepherd <[EMAIL PROTECTED]>
To: Discussion of Numerical Python
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMA
Hey all,
We started to try and compile the numpy module on an embedded PowerPC
Xilinx board with no luck. This is one of the errors I get when I try
to build the module on-board. It is due to the fact that the compiler
is located in a different location than the original compiler for python
Okay, I manually changed defined(linux) to defined(__GLIBC__). I still
get the same error with "_capi.c". It keeps trying to #include
. Any other things I can change to try to prevent the problem?
Thanks,
David
-Dave
Error output:
creating build/temp.linux-ppc-2.5/numpy/lib
creating build/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shepherd wrote:
> The second part of the patch is failing:
>
> # patch -p0 < ../uclibc-fenv.patch
> patching file numpy/core/include/numpy/ufuncobject.h
> patching file numpy/numarray/_capi.c
> Hunk #1 FAILED at 224.
> Hunk #2 FAILED at 2937.
>
The second part of the patch is failing:
# patch -p0 < ../uclibc-fenv.patch
patching file numpy/core/include/numpy/ufuncobject.h
patching file numpy/numarray/_capi.c
Hunk #1 FAILED at 224.
Hunk #2 FAILED at 2937.
2 out of 2 hunks FAILED -- saving rejects to file numpy/numarray/_capi.c.rej
#
I at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shepherd wrote:
> You know, looking at the core it looks like it has something to do with
> the "define(linux)" statement. I am running linux, but its a buildroot
> (uclibc) rootfs. Let me know if you need anymore information. Thanks.
>
> D
You know, looking at the core it looks like it has something to do with
the "define(linux)" statement. I am running linux, but its a buildroot
(uclibc) rootfs. Let me know if you need anymore information. Thanks.
Dave
David Shepherd wrote:
> Well, I get further into the compile process, but
Well, I get further into the compile process, but now it fails on
another gcc compile operations. This is essentially the same error
message I was getting before. It tries to #include , but does
not find it (it shouldn't be including it anyway, as you said). This
time it fails when trying to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Shepherd wrote:
> Hey all,
>
> We started to try and compile the numpy module on an embedded PowerPC
> Xilinx board with no luck. This is one of the errors I get when I try
> to build the module on-board. It is due to the fact that the compi
Hey all,
We started to try and compile the numpy module on an embedded PowerPC
Xilinx board with no luck. This is one of the errors I get when I try
to build the module on-board. It is due to the fact that the compiler
is located in a different location than the original compiler for python
14 matches
Mail list logo
