Error Error In Opening The Library Module File. Dfport
Contents |
together with DVF 6.1 and CXML. CXML already contains BLAS libraries. Should one delete the LAPACK BLAS libraries? Markus Wed, 18 Jun error in opening the compiled module file. check include paths. netcdf 1902 08:00:00 GMT Mark#2 / 3 How to install LAPACK with DVF 6.1
Fortran Include Paths
and CXML I tried to link Lapack V3.0 against DFV libs but get an error in second.f: second.f(16): Error: Error fortran .mod file in opening the library module file. [DFPORT] USE DFPORT NMAKE: fatal error U1077:'df': Return-Code:'0x1' STOP .... Can anybody help Markus Wed, 18 Jun 1902 08:00:00 GMT Steve Lione#3 / 3 How to install
Fortran Module
LAPACK with DVF 6.1 and CXML Quote:>I tried to link Lapack V3.0 against DFV libs but get an error in second.f: >second.f(16): Error: Error in opening the library module file. [DFPORT] USE >DFPORT >NMAKE: fatal error U1077:'df': Return-Code:'0x1' >STOP .... This suggests that you have not executed the DFVARS.BAT file which defines environment variables used by the compiler to locate things such as predefined module files. The "fortran command prompt" entry in the Visual Fortran program group will create a command prompt window with those variables defined. This is not needed when building from the Developer Studio environment - but make sure that you have run Per-User Setup (once) if you are not the user who installed DVF. Fortran Engineering Compaq Computer Corporation, Nashua NH Compaq Fortran web site: http://www.compaq.com/fortran Compaq Fortran Message Board: http://forum.compaq.com:80/mb8/system/fortran_login.html Wed, 18 Jun 1902 08:00:00 GMT Page 1 of 1 [ 3 post ] Relevant Pages 1. Installing Lapack libraries on DVF for PC 2. Problems linking using CVF and the LAPACK in CXML and Intel's MKL 3. dvf 6.1 update on cd, when? 4. Problem with Loading/unloading dll's (DVF 6.1) 5. Visual C++ calling Fortran / DVF 6.1: error LNK2001 6. DVF 6.1 now available 7. Can I not install Order Analysis Toolsett in LabVIEW 6.1 8. Memory Error when installing labview 6.1 9. cannot find device or file error when installing 6.1 from cd or from hard drive 10. LabVIEW 6.1 will not install 11. I can't get LabVIEW 6.1 to install properly on a computer running XP. 12. do I have to uninstall Labview 5.1 to install 6.1 Po
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only http://computer-programming-forum.com/49-fortran/d74ea3d3b17255e5.htm takes a minute: Sign up How to reuse Fortran modules without copying source or creating libraries up vote 2 down vote favorite 2 I'm having trouble understanding if/how to share code among several Fortran projects without building libraries or duplicating source code. I am using Eclipse/Photran with the Intel compiler (ifort) on a linux system, but I believe I'm having a http://stackoverflow.com/questions/16352319/how-to-reuse-fortran-modules-without-copying-source-or-creating-libraries bigger conceptual problem with modules than with the specific tools. Here's a simple example: In ~/workspace/cow I have a source directory (src) containing cow.f90 (the PROGRAM) and two modules m_graze and m_moo in m_graze.f90 and m_moo.f90, respectively. This project builds and links properly to create the executable 'cow'. The executable and modules (m_graze.mod and m_moo.mod) are stored in ~/workspace/cow/Debug and object files are stored under ~/workspace/cow/Debug/src Later, I create ~/workplace/sheep and have src/sheep.f90 as the program and src/m_baa.f90 as the module m_baa. I want to 'use m_graze, only: ruminate' in sheep.f90 to get access to the ruminate() subroutine. I could just copy m_graze.f90 but that could lead to code getting out of sync and doesn't take into account any dependencies m_graze might have. For these reasons, I'd rather leave m_graze in the cow project and compile and link sheep.f90 against it. If I try to compile the sheep project, I'll get an error like: error #7002: Error in opening the compiled module file. Check INCLUDE paths. [M_GRAZE] Under Properties:Project References for sheep, I can select the cow project. Under Properties:Fortran Bui
exciting Other Packages How to reach us Contact Forum Development Developers Space Manage Wiki Internal edit this panel | http://exciting-code.org/forum/t-702796/compilation-error:can-t-open-module-file-modinput-mod recent changes Compilation error: "Can't open module file 'modinput.mod'" Forum » Forum / Support Questions » Compilation error: "Can't open module file 'modinput.mod'" Started by: Michael Wainberg Date: 01 Oct 2013 20:09 Number of posts: 10 RSS: New posts Unfold All Fold All More Options Edit Title & Description Stickness Lock Thread Move Thread Fold error in Compilation error: "Can't open module file 'modinput.mod'" Michael Wainberg 01 Oct 2013 20:09 I am compiling exciting for Linux Mint 1464-bit (which is derived from Ubuntu 12.10). I installed gfortran, Lapack/Blas (libblas-dev, libatlas-dev, liblapack-dev) and xsltproc. In setup.pl, I selected gfortran as the compiler and turned off MPI and SMP. When running make, I receive the error in opening following error: make[3]: Entering directory `/home/user/exciting/build/serial' gfortran -O3 -march=native -cpp -DXS -DISO -DTETRA -DLIBXC -I./finclude -c -I../../src ../../src/mod_potential_and_density.F90 ../../src/mod_potential_and_density.F90:11.10: Use modinput 1 Fatal Error: Can't open module file 'modinput.mod' for reading at (1): No such file or directory make[3]: *** [mod_potential_and_density.o] Error 1 Here is my /build/make.inc file: F90=gfortran F77=$(F90) F90_OPTS = -O3 -march=native # -flto F77_OPTS = $(F90_OPTS) CPP_ON_OPT = -cpp -DXS -DISO -DTETRA -DLIBXC LIB_ARP =libarpack.a LIB_LPK = -L./ -llapack -lblas LIB_FFT = fftlib.a LIB_BZINT= libbzint.a LIBS= $(LIB_ARP) $(LIB_LPK) $(LIB_FFT) $(LIB_BZINT) # -flto -fwhole-program F90_DEBUGOPTS=-g -fbounds-check -fbacktrace -Wall F77_DEBUGOPTS= $(F90_DEBUGOPTS) #Ignore if you don't have MPI or smplibs MPIF90=mpif90 MPIF90_OPTS=$(F90_OPTS) $(CPP_ON_OPT) -DMPI -DMPIRHO -DMPISEC F77MT=$(F77) F90MT=$(F90) SMP_LIBS=$(LIBS) SMPF90_OPTS=-fopenmp $(F90_OPTS) SMPF77_OPTS=$(SMPF90_OPTS) BUILDMPI=false BUILDSMP=false Do you have any suggestions on how to fix this error? Thanks, Michael Reply Options Unfold Compilation error: "Can't open module file 'modinput.mod'" by Michael Wainberg, 01 Oct 2013 20:09 Fold Re: Compilation error: "Can't open module file 'modinput.mod'" DmitriiNabok 02 Oct 2013 11:21 Dear Michael, First step would b
be down. Please try the request again. Your cache administrator is webmaster. Generated Tue, 11 Oct 2016 11:33:34 GMT by s_wx1131 (squid/3.5.20)