Le dimanche 30 novembre 2008 à 14:47 +0900, David Cournapeau a écrit :
> Fabrice Silva wrote:
> >
> > A way of solving this issue was to move the shared object file to
> > another directory. But I want to figure out what is happening exactly.
> > Googling a lot indicates that selinux would be the c
Fabrice Silva wrote:
>
> A way of solving this issue was to move the shared object file to
> another directory. But I want to figure out what is happening exactly.
> Googling a lot indicates that selinux would be the cause of this
> issue...
> Has anyone a suggestion?
>
Disabling selinux ?
Dav
Hi all,
I am facing this old problem again :
Fabrice Silva a écrit :
> Dear all
> I've tried to run f2py on a fortran file which used to be usable from
> python some months ago.
> Following command line are applied with success (no errors raised) :
> f2py -m modulename -c --f90exec=gnu95
Le lundi 23 juin 2008 à 14:10 +0200, Fabrice Silva a écrit :
> > I don't have ideas what is causing this import error. Try
> > the instructions above, may be it is due to some compile object
> > conflicts.
> The only posts on mailing lists I've read mention security policies
> (SElinux) and /tmp e
Le lundi 23 juin 2008 à 14:00 +0300, Pearu Peterson a écrit :
> First, it is not clear what compiler is f95. If it is gfortran, then
> use the command
> f2py -m modulename -c --fcompiler=gnu95 tmpo.f
>
> If it is something else, check the output of
>
> f2py -c --help-fcompiler
>
> and use ap
On Mon, June 23, 2008 10:38 am, Fabrice Silva wrote:
> Dear all
> I've tried to run f2py on a fortran file which used to be usable from
> python some months ago.
> Following command lines are applied with success (no errors raised) :
> f2py -m modulename -h tmpo.pyf --overwrite-signature
Dear all
I've tried to run f2py on a fortran file which used to be usable from
python some months ago.
Following command lines are applied with success (no errors raised) :
f2py -m modulename -h tmpo.pyf --overwrite-signature tmpo.f
f2py -m modulename -c --f90exec=/usr/bin/f95 tmp
