It's just kinda standard. Just like you can specify different c/c++ compilers and flags, you can do the same with f77/f90.
-Ben On May 31, 2013, at 4:46 PM, "Subramanya Sadasiva" <[email protected]<mailto:[email protected]>> wrote: Hi Ben, I did that , and things are building. Thanks! Is there a particular reason to have F77 and F handled through separate compilers? Subramanya Subramanya G Sadasiva, Graduate Research Assistant, Hierarchical Design and Characterization Laboratory, School of Mechanical Engineering, Purdue University. "The art of structure is where to put the holes" Robert Le Ricolais, 1894-1977 On Fri, May 31, 2013 at 5:33 PM, Kirk, Benjamin (JSC-EG311) <[email protected]<mailto:[email protected]>> wrote: On May 31, 2013, at 4:25 PM, Subramanya Sadasiva <[email protected]<mailto:[email protected]>> wrote: > PPF77 forbind/src/libdbg_la-addrwrap.lo > ../../../../libtool: line 1122: no: command not found > make[2]: *** [forbind/src/libdbg_la-addrwrap.lo] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 > > > I am using the macports compilers (set using the CC, FC, and CXX > environment variables.) I haven't gotten this error in the past. Has > anybody seen this? Sounds like it is failing to find a Fortran 77 compiler. I'll try and remember to check for this case and set the Fortran 77 compiler to the $FC value when it can't find one… But in the meantime, in addition to FC, please also specify F77 e.g., $ ./configure CXX=g++ CC=gcc FC=gfortran F77=gfortran -Ben ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
