[f2py] Re: 64-bit problems - 'undefined symbol'
alan at codescape.net
Sat Jun 21 19:22:43 EEST 2008
Never mind, I fixed the problem - I was assuming that the Ubuntu dev's
wouldn't be stupid enough to ship a broken Numpy. Once I had the same issue
on 32-bit I downloaded 1.1.0 from sourceforge and installed that, and
everything works fine on both platforms.
On Sun, Jun 15, 2008 at 6:03 PM, Alan Briolat <alan at codescape.net> wrote:
> I've got some F90 code I've been developing a Python app around on 32-bit
> for a while now, but recently moved to 64-bit on my development machine.
> The first problem I hit was while linking:
> /usr/bin/ld: params_veg.o: relocation R_X86_64_32 against `a local symbol'
> can not be used when making a shared object; recompile with -fPIC
> After adding -fPIC to the compile command, I ended up with another error,
> this time when trying to import into Python:
> File "/home/alan/development/SEI/DO3SE/ui/dose.py", line 1, in <module>
> from dose_f import *
> ImportError: /home/alan/development/SEI/DO3SE/ui/dose_f.so: undefined
> symbol: f2pyinitparams_site_
> At the moment, I use F2PY to generate the spec file, gfortran -fPIC to
> compile the parts, and then F2PY with --fcompiler=3Dgnu95 (which links it=
> together). This all works fine under 32-bit (although I haven't used -fP=
> under 32-bit - could this be the problem?). Does anybody know what
> f2pyinitparam_site_ might be generated from? (I have an F90 module called
> param_site.) What might cause this to not exist?
> Thanks in advance to anybody who can point me in the right direction of
> what I should be ripping apart and testing.
> Alan Briolat (http://www.codescape.net/)
> 2nd Year, Computer Systems and Software Engineering (MEng), University of
> York, UK
Alan Briolat (http://www.codescape.net/)
2nd Year, Computer Systems and Software Engineering (MEng), University of
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the f2py-users