On 2009-09-25 15:36 , Arthur Bousquet wrote:
> Thanks a lot for you help. Now it is working, I downloaded the gfortran
> from http://hpc.sourceforge.net/.
I will take the opportunity to steal Robert's line and say that the
gfortran available from that site has had numerous problems in the past.
Thanks a lot for you help. Now it is working, I downloaded the gfortran from
http://hpc.sourceforge.net/.
Best regards,
Arthur
On Fri, Sep 25, 2009 at 3:49 PM, Arthur Bousquet wrote:
> How can I add the flags ?
>
> Thank
>
> Arthur
>
>
> On Fri, Sep 25, 2009 at 3:46 PM, Robert Kern wrote:
>
>> O
On Fri, Sep 25, 2009 at 14:44, Arthur Bousquet wrote:
> $ file libsw.so gives :
>
> libsw.so: Mach-O bundle i386
>
> How can I change it ? Is it because of my gfortran ?
Your gfortran is probably still configured to make x86 executables by
default. Try recompiling libsw.so with the flags
-arch
$ file libsw.so gives :
libsw.so: Mach-O bundle i386
How can I change it ? Is it because of my gfortran ?
Thanks.
- Arthur
On Fri, Sep 25, 2009 at 3:30 PM, Robert Kern wrote:
> On Fri, Sep 25, 2009 at 14:08, Arthur Bousquet
> wrote:
> > Ok, so I re-compiled python (without framework), numpy
On Fri, Sep 25, 2009 at 14:08, Arthur Bousquet wrote:
> Ok, so I re-compiled python (without framework), numpy,... So I can compile
> my lib (libsw) now, bu I can't called it from python. I got this error :
>
> Arths-MacBook-Pro:run_1 arthbous$ ./run.sh
> Traceback (most recent call last):
> Fil
Ok, so I re-compiled python (without framework), numpy,... So I can compile
my lib (libsw) now, bu I can't called it from python. I got this error :
Arths-MacBook-Pro:run_1 arthbous$ ./run.sh
Traceback (most recent call last):
File "../main.py", line 23, in
import libsw as lsw
ImportError:
On Fri, Sep 25, 2009 at 13:43, Arthur Bousquet wrote:
> Thank you a lot for your help. So I deleted as you said, but then I do with
> --enable-framework for python, at the make there is an error :
>
> ln -fsn 2.6 Python.framework/Versions/Current
> ln -fsn Versions/Current/Python Python.framework/
Thank you a lot for your help. So I deleted as you said, but then I do with
--enable-framework for python, at the make there is an error :
ln -fsn 2.6 Python.framework/Versions/Current
ln -fsn Versions/Current/Python Python.framework/Python
ln -fsn Versions/Current/Headers Python.framework/Headers
On Fri, Sep 25, 2009 at 13:02, Arthur Bousquet wrote:
> I got :
>
> Arths-MacBook-Pro:~ arthbous$ python2.6
> ActivePython 2.6.2.2 (ActiveState Software Inc.) based on
> Python 2.6.2 (r262:71600, Apr 24 2009, 21:40:46)
> [GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin
> Type "help", "copyr
I got :
Arths-MacBook-Pro:~ arthbous$ python2.6
ActivePython 2.6.2.2 (ActiveState Software Inc.) based on
Python 2.6.2 (r262:71600, Apr 24 2009, 21:40:46)
[GCC 4.0.1 (Apple Computer, Inc. build 5250)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>
On Fri, Sep 25, 2009 at 12:55, Arthur Bousquet wrote:
> The first line of /usr/local/f2py2.6 is :
>
> #!/usr/bin/env python2.6
> # See http://cens.ioc.ee/projects/f2py2e/
And exactly which python2.6 executable do you get when you type
$ python 2.6
? Try printing sys.executable:
$ python
Python
The first line of /usr/local/f2py2.6 is :
#!/usr/bin/env python2.6
# See http://cens.ioc.ee/projects/f2py2e/
- Arthur
On Fri, Sep 25, 2009 at 1:51 PM, Robert Kern wrote:
> On Fri, Sep 25, 2009 at 12:35, Arthur Bousquet
> wrote:
> > Thank you. So here the command :
> >
> > Arths-MacBook-Pro:~
On Fri, Sep 25, 2009 at 12:35, Arthur Bousquet wrote:
> Thank you. So here the command :
>
> Arths-MacBook-Pro:~ arthbous$ grep isysroot
> /Library/Frameworks/Python.framework/Versions/Current/lib/python2.6/config/Makefile
> BASECFLAGS= -arch ppc -arch i386 -isysroot
> /Developer/SDKs/MacOSX10.
Thank you. So here the command :
Arths-MacBook-Pro:~ arthbous$ grep isysroot
/Library/Frameworks/Python.framework/Versions/Current/lib/python2.6/config/Makefile
BASECFLAGS=-arch ppc -arch i386 -isysroot
/Developer/SDKs/MacOSX10.4u.sdk -fno-strict-aliasing -fPIC -fno-common
-dynamic
LDFLAGS=
On Fri, Sep 25, 2009 at 12:24, Arthur Bousquet wrote:
> Sorry about that.
>
> I typed in the Terminal "grep isysroot" and it is like nothing is happening.
> The terminal is still working but does not give any response.
Ah, sorry about that. The command got wordwrapped. Cancel that command
using C
Sorry about that.
I typed in the Terminal "grep isysroot" and it is like nothing is happening.
The terminal is still working but does not give any response.
Arthur
On Fri, Sep 25, 2009 at 1:21 PM, Robert Kern wrote:
> On Fri, Sep 25, 2009 at 12:17, Arthur Bousquet
> wrote:
> > $ grep isysroot
On Fri, Sep 25, 2009 at 12:17, Arthur Bousquet wrote:
> $ grep isysroot
>
> does not work on my computer.
What does that mean? Exactly what did you type and exactly what
response did you get? Please, never just say that something "does not
work".
--
Robert Kern
"I have come to believe that the
$ grep isysroot
does not work on my computer.
Arthur
On Fri, Sep 25, 2009 at 12:27 PM, Robert Kern wrote:
> On Fri, Sep 25, 2009 at 11:19, Arthur Bousquet
> wrote:
> > Here my full error : http://dl.getdropbox.com/u/541149/error_f2py.txt
>
> /Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.
On Fri, Sep 25, 2009 at 11:19, Arthur Bousquet wrote:
> Here my full error : http://dl.getdropbox.com/u/541149/error_f2py.txt
/Developer/SDKs/MacOSX10.4u.sdk/usr/include/stdarg.h:4:25: error:
stdarg.h: No such file or directory
I didn't think that MacOSX10.4u.sdk existed on Snow Leopard. The
"-
Here my full error : http://dl.getdropbox.com/u/541149/error_f2py.txt
Thank you,
Arthur
On Fri, Sep 25, 2009 at 11:59 AM, Robert Kern wrote:
> On Fri, Sep 25, 2009 at 10:48, Arthur Bousquet
> wrote:
> > I used compiler=gcc, here is the command :
> >
> > f2py2.6 --fcompiler=gfortran --compiler=
On Fri, Sep 25, 2009 at 10:48, Arthur Bousquet wrote:
> I used compiler=gcc, here is the command :
>
> f2py2.6 --fcompiler=gfortran --compiler=gcc -DF2PY_REPORT_ON_ARRAY_COPY=1 -m
> libsw -c file1.f90 file2.f90
>
> Ok so you said that "--compiler=gcc" is not a command ?
Correct. --compiler= does
I used compiler=gcc, here is the command :
f2py2.6 --fcompiler=gfortran --compiler=gcc -DF2PY_REPORT_ON_ARRAY_COPY=1 -m
libsw -c file1.f90 file2.f90
Ok so you said that "--compiler=gcc" is not a command ?
So I removed the line "--compiler=gcc", and I got a new error :
error: Command "gcc -arch
On Fri, Sep 25, 2009 at 10:19, Arthur Bousquet wrote:
> Hello,
>
> I have a Mac with snow leopard 10.6. I compiled Python2.6.2, numpy1.3 and
> matplotlib from the sources.
> I tried to compiled a library (named libsw), that I have made in fortran,
> with f2py but I got the following error :
>
> ru
Hello,
I have a Mac with snow leopard 10.6. I compiled Python2.6.2, numpy1.3 and
matplotlib from the sources.
I tried to compiled a library (named libsw), that I have made in fortran,
with f2py but I got the following error :
running build_ext
error: don't know how to compile C/C++ code on platfo
24 matches
Mail list logo