[SciPy-dev] scipy distutils from CVS does not build code for fortran libraries

Pearu Peterson pearu at scipy.org
Fri Mar 26 09:53:58 CST 2004



On Fri, 26 Mar 2004, [ISO-8859-15] Berthold Höllmann wrote:

> Hello,
> 
> I tried to compile a project of ours under solaris5. I gave
> 
> PYTHONPATH="/home/hoel/work/GLPy/lib:/home/hoel/work/GLPy/build/lib.solaris-2.8-sun4u-2.2:" python setup_Engmodel.py config_fc --fcompiler=sun build_src build_clib build_ext
> ...
> customize SunFCompiler
> customize SunFCompiler using build_clib
> ********************************************************************************
> scipy_distutils.sunfcompiler.SunFCompiler
> archiver        = ['ar', '-cr']
> version_cmd     = ['f90', '-V']
> compiler_f77    = ['f90', '-f77', '-ftrap=%none', '-xcode=pic32']
> linker_so       = ['f90', '-Bdynamic', '-G']
> compiler_fix    = ['f90', '-fixed', '-xcode=pic32']
> ranlib          = ['ranlib']
> compiler_f90    = ['f90', '-xcode=pic32']
> version         = None
> libraries       = ['fsu', 'sunmath', 'mvec', 'f77compat']
> library_dirs    = []
> object_switch   = '-o '
> compile_switch  = '-c'
> include_dirs    = []
> ********************************************************************************
> building 'engforcegen' library
> compling Fortran sources
> creating build.Engmodel/temp.solaris-2.8-sun4u-2.2
> creating build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib
> creating build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen
> f90:f77: lib/engforcegen/engforcelib.f
> f90:f77: lib/engforcegen/totalforces.f
> f90:f77: lib/engforcegen/foucoefftable.f
> f90:f77: lib/engforcegen/esrheader.f
> f90:f77: lib/engforcegen/pphase.f
> f90:f77: lib/engforcegen/excnodes.f
> f90:f77: lib/engforcegen/fourier.f
> f90:f77: lib/engforcegen/cylphase.f
> f90:f77: lib/engforcegen/esrdata.f
> f90:f77: lib/engforcegen/normangle.f
> f90:f77: lib/engforcegen/cylforces.f
> ar: adding 11 object files to build.Engmodel/temp.solaris-2.8-sun4u-2.2/libengforcegen.a
> error: Command "ar -cr build.Engmodel/temp.solaris-2.8-sun4u-2.2/libengforcegen.a build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/engforcelib.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/cylforces.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/cylphase.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/esrdata.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/esrheader.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/excnodes.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/foucoefftable.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/fourier.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/pphase.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/totalforces.o build.Engmodel/temp.solaris-2.8-sun4u-2.2/lib/engforcegen/normangle.o" failed with exit status 1
> 
> all the ".o" files are missing. Just another problem with "exec_command"?

No, I would not think so. On linux building scipy works fine with a
recent CVS copy. So, could you find out where these ".o" files end up?

Btw, using

  PYTHONPATH=.... python setup_Engmodel.py config_fc --fcompiler=sun build

should work just fine (I mean instead of 'build_src ...').

Pearu




More information about the Scipy-dev mailing list