Does anyone know how to run
python setup.py build
and have gfortran used? It is in my path.
Mathew
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
Mathew Yeates wrote:
> Does anyone know how to run
> python setup.py build
> and have gfortran used? It is in my path.
python setup.py config_fc --fcompiler=gnu95 build
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own
result
Found executable /usr/bin/g77
gnu: no Fortran 90 compiler found
Something is *broken*.
Robert Kern wrote:
> Mathew Yeates wrote:
>
>> Does anyone know how to run
>> python setup.py build
>> and have gfortran used? It is in my path.
>>
>
> python setup.py config_fc --fcompiler=gnu9
Mathew Yeates wrote:
> result
> Found executable /usr/bin/g77
> gnu: no Fortran 90 compiler found
>
> Something is *broken*.
Then please provide us with enough information to help you. What platform are
you on? Exactly what command did you execute? Exactly what output did you get
(please copy-and
Mathew Yeates wrote:
> result
> Found executable /usr/bin/g77
> gnu: no Fortran 90 compiler found
>
> Something is *broken*.
Also, what version of numpy are you using?
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own
I have found that setting my F77 environment variable to gfortran is
also sufficient.
> setenv F77 gfortran
> python setup.py install
Chris
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy
Thanks for anyones help. I've been trying to figure this out for some
time now. Stepping through distutils code is a bummer.
-bash-3.1$ uname -a
Linux mu.jpl.nasa.gov 2.6.17-5mdv #1 SMP Wed Sep 13 14:28:02 EDT 2006
x86_64 Dual-Core AMD Opteron(tm) Processor 2220 SE GNU/Linux
-bash-3.1$ gfortran
Mathew Yeates wrote:
>> -bash-3.1$ python setup.py config_fc --fcompiler=gnu95 build 2>&1 |tee out
Did you forget to attach a file?
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma
that is made terrible by our own mad attempt to interpret it as thoug
Christopher Hanley wrote:
> I have found that setting my F77 environment variable to gfortran is
> also sufficient.
>
> > setenv F77 gfortran
> > python setup.py install
That might work okay for building scipy and other packages that only actually
have FORTRAN-77 code; however, I suspect that
No.
My PC crashed. I swear I have a virus on this machine. Been that kinda
weekend
Not particularly illuminating but here it is:
Running from numpy source directory.
F2PY Version 2_3875
blas_opt_info:
blas_mkl_info:
libraries mkl,vml,guide not found in /u/vento0/myeates/lib
NOT AVAILABLE
atl
More info:
I tried Chris' suggestion , i.e. export F77=gfortran
And now I get
Found executable /u/vento0/myeates/bin/gfortran
gnu: no Fortran 90 compiler found
Found executable /usr/bin/g77
Mathew Yeates wrote:
> No.
> My PC crashed. I swear I have a virus on this machine. Been that kinda
>
Even more info!
I am using numpy gotten from svn on Wed or Thurs.
Mathew Yeates wrote:
> More info:
> I tried Chris' suggestion , i.e. export F77=gfortran
>
> And now I get
>
> Found executable /u/vento0/myeates/bin/gfortran
> gnu: no Fortran 90 compiler found
> Found executable /usr/bin/g77
>
>
>
Mathew Yeates wrote:
> More info:
> I tried Chris' suggestion , i.e. export F77=gfortran
>
> And now I get
>
> Found executable /u/vento0/myeates/bin/gfortran
> gnu: no Fortran 90 compiler found
> Found executable /usr/bin/g77
Are you just trying to build numpy? Do you actually need a Fortran co
Mathew Yeates wrote:
> Even more info!
> I am using numpy gotten from svn on Wed or Thurs.
Try to use numpy 1.0.3. There was a large set of changes to numpy.distutils
after that release that have proven to be somewhat fragile. If 1.0.3 works,
please enter a ticket into our Trac. Provide the inform
This is slightly off-topic, but probably of interest to anyone reading
this thread:
Is there any reason why we don't use --fcompiler=gfortran as an alias
for --fcompiler=gfortran (and --fcompiler=g77 as an alias for
--fcompiler=gnu, for that matter)?
Those seem to me to be much more mnemonic n
I wrote:
> This is slightly off-topic, but probably of interest to anyone reading
> this thread:
>
> Is there any reason why we don't use --fcompiler=gfortran as an alias
> for --fcompiler=gfortran (and --fcompiler=g77 as an alias for
> --fcompiler=gnu, for that matter)?
But, sorry, of course
On Jul 2, 2007, at 12:02 , Andrew Jaffe wrote:
> I wrote:
>
>> This is slightly off-topic, but probably of interest to anyone
>> reading
>> this thread:
>>
>> Is there any reason why we don't use --fcompiler=gfortran as an alias
>> for --fcompiler=gfortran (and --fcompiler=g77 as an alias for
>>
nope. try again
% python setup.py -v config_fc --fcompiler=gfortran install
Running from numpy source directory.
non-existing path in 'numpy/distutils': 'site.cfg'
F2PY Version 2_3882
blas_opt_info:
blas_mkl_info:
( library_dirs = /u/vento0/myeates/lib:/usr/lib )
( include_dirs = /usr/include:/u/
18 matches
Mail list logo
