I get the following error message when running the program: cp -f ..//lib/modules/an_header.f90 an_header.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include an_header.f90 gfortran: unrecognized option '-convert=big_endian' rm -f an_header.f90 cp -f ..//lib/charutils.f90 charutils.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include charutils.f90 gfortran: unrecognized option '-convert=big_endian' rm -f charutils.f90 cp -f ..//lib/dateutils.f90 dateutils.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include dateutils.f90 gfortran: unrecognized option '-convert=big_endian' rm -f dateutils.f90 gcc -c -O2 -DPC_LINUX1 -I..//include ..//lib/dted.c ..//lib/dted.c: In function ‘readdted1_’: ..//lib/dted.c:230: warning: ignoring return value of ‘fscanf’, declared with attribute warn_unused_result ..//lib/dted.c:249: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result gcc -c -O2 -DPC_LINUX1 -I..//include ..//eff/eenviron.c ..//eff/eenviron.c: In function ‘fegetenv_’: ..//eff/eenviron.c:144: warning: incompatible implicit declaration of built-in function ‘exit’ cp -f ..//lib/error_mess.f90 error_mess.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include error_mess.f90 gfortran: unrecognized option '-convert=big_endian' rm -f error_mess.f90 cp -f ..//lib/filelist.F90 filelist.F90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include -DPC_LINUX1 filelist.F90 gfortran: unrecognized option '-convert=big_endian' f951: warning: command line option "-FR" is valid for C/C++/ObjC/ObjC++ but not for Fortran rm -f filelist.F90 cp -f ..//lib/getvar.f90 getvar.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include getvar.f90 gfortran: unrecognized option '-convert=big_endian' rm -f getvar.f90 cp -f ..//lib/htint-opt.f90 htint-opt.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include htint-opt.f90 gfortran: unrecognized option '-convert=big_endian' rm -f htint-opt.f90 cp -f ..//lib/interp_lib.f90 interp_lib.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include interp_lib.f90 gfortran: unrecognized option '-convert=big_endian' rm -f interp_lib.f90 cp -f ..//lib/map_proj.f90 map_proj.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include map_proj.f90 gfortran: unrecognized option '-convert=big_endian' rm -f map_proj.f90 cp -f ..//lib/numutils.f90 numutils.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include numutils.f90 gfortran: unrecognized option '-convert=big_endian' rm -f numutils.f90 gcc -c -O2 -DPC_LINUX1 -I..//include ..//lib/parlib.c cp -f ..//lib/polarst.f90 polarst.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include polarst.f90 gfortran: unrecognized option '-convert=big_endian' rm -f polarst.f90 cp -f ..//lib/rsys.F90 rsys.F90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include -DPC_LINUX1 rsys.F90 gfortran: unrecognized option '-convert=big_endian' f951: warning: command line option "-FR" is valid for C/C++/ObjC/ObjC++ but not for Fortran rm -f rsys.F90 cp -f ..//lib/therm_lib.f90 therm_lib.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include therm_lib.f90 gfortran: unrecognized option '-convert=big_endian' rm -f therm_lib.f90 gcc -c -O2 -DPC_LINUX1 -I..//include ..//lib/tmpname.c ..//lib/tmpname.c: In function ‘form_tmpname_’: ..//lib/tmpname.c:29: warning: incompatible implicit declaration of built-in function ‘strlen’ gcc -c -O2 -DPC_LINUX1 -I..//include ..//lib/utils_c.c ..//lib/utils_c.c: In function ‘rams_c_read_’: ..//lib/utils_c.c:169: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result ..//lib/utils_c.c: In function ‘rams_c_read_char_’: ..//lib/utils_c.c:181: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result ..//lib/utils_c.c: In function ‘vfirecr_’: ..//lib/utils_c.c:213: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result ..//lib/utils_c.c:217: warning: ignoring return value of ‘fread’, declared with attribute warn_unused_result cp -f ..//lib/utils_f.f90 utils_f.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include utils_f.f90 gfortran: unrecognized option '-convert=big_endian' rm -f utils_f.f90 cp -f ..//lib/vformat.f90 vformat.f90 gfortran -c -FR -O2 -convert=big_endian -g -I..//include vformat.f90 gfortran: unrecognized option '-convert=big_endian' rm -f vformat.f90 ar rs /media/WRFDisk/WRF3.2/WRFV3/Prep_sources_chem_cptec_wrf/utils/bin//libutils-2.0-opt.a an_header.o charutils.o dateutils.o dted.o eenviron.o error_mess.o filelist.o getvar.o htint-opt.o interp_lib.o map_proj.o numutils.o parlib.o polarst.o rsys.o therm_lib.o tmpname.o utils_c.o utils_f.o vformat.o ar: creating /media/WRFDisk/WRF3.2/WRFV3/Prep_sources_chem_cptec_wrf/utils/bin//libutils-2.0-opt.a
Finished building === /media/WRFDisk/WRF3.2/WRFV3/Prep_sources_chem_cptec_wrf/utils/bin//libutils-2.0-opt.a Here is the makefile that I am using: #----------------- LINUX INTEL FORTRAN-95 Compiler/GCC --------- CMACH=PC_LINUX1 F_COMP=gfortran C_COMP=gcc LOADER=gfortran C_LOADER=gcc LIBS= MOD_EXT=mod # Compiler options F_OPTS=-FR -O2 -convert=big_endian $(NCDF_LIBS) -g C_OPTS=-O2 LOADER_OPTS= C_LOADER_OPTS=-v #----------------------------------------------------------------- Should I use this one instead? #----------------- LINUX Portland Group pgf77/gcc --------------- #CMACH=PC_LINUX1 #F_COMP=gfortran #C_COMP=gcc #LOADER=gfortran #C_LOADER=gcc #LIBS= #MOD_EXT=mod # #F_OPTS= -O3 -fastsse #C_OPTS= -O3 -DUNDERSCORE -DLITTLE #LOADER_OPTS= -v -Mstatic -O3 -fastsse #----------------------------------------------------------------- Thanks, Jason On Tue, Aug 10, 2010 at 2:25 PM, Ambroff Linden <ambr...@lindenlab.com>wrote: > For that particular option, see -fconvert in the gfortran man page. > You can specify the representation of data files with > -fconvert=<representation>, where representation is one of: > > * native (little-endian on your little-endian PC) > * swap (opposite of your systems binary representation) > * little-endian > * big-endian > > For example, if you were passing "-convert big_endian" to your fortran > compiler, you should switch to "-fconvert=big-endian" for gfortran. > > I'd be surprised if that's your only problem though. You might want to > look up the documentation for all of the options you are using with > the original target FORTRAN implementation. You can compare that with > the gfortran man page to find equivalent settings for gfortran. > > -Kyle > > On Tue, Aug 10, 2010 at 10:21 AM, Jason Snyder <jmssny...@ucdavis.edu> > wrote: > > > > would fixing the error mentioned by the statement: > > > > gfortran: unrecognized option '-convert' > > > > help with this issue. > > > > I have ubuntu linux which operates with a gfortran fortran compiler and > gcc c compiler. > > > > I am not sure how to approach handling the issue with the above error > statement. Do I have to install something on my computer or do I have to > use another setting for compiling in the make file? > > > > I am currently using the one for linux intel. What do I use for ubuntu? > > > > Thanks, > > > > Jason > > > > On Tue, Aug 10, 2010 at 7:39 AM, Steven Peckham <steven.peck...@noaa.gov> > wrote: > >> > >> Jason, > >> It would appear that you made some changes to the prep_chem_sources > include.mk file that do not work for your compiler. > >> > >> gfortran: unrecognized option '-convert' > >> > >> This is why you are getting an error when compiling the code. > >> The solution is that you should edit the make include file and set the > options that work for your compiler on your compute platform. > >> Steven > >> > >> > >> On Aug 9, 2010, at 6:57 PM, Jason Snyder wrote: > >> > >> I configuring the prep-chem-sources and got the following error message: > >> > >> /utils/bin$ make -f Make_utils > >> cp -f ..//lib/modules/an_header.f90 an_header.f90 > >> gfortra! n -c -FR bsp; -g -I..//include an_header.f90 > >> gfortran: big_endian: No such file or directory > >> gfortran: unrecognized option '-convert' > >> make: *** [an_header.o] Error 1 > >> > >> What does this mean and how do I resolve this issue? I did format the > include.mk so that it would run with the gfortran and gcc compilers that I > have with ubuntu linux. > >> > >> Anyway, let me know how to approach this situation. > >> > >> thanks, > >> > >> Jason > >> > >> On Sun, Aug 8, 2010 at 12:57 AM, Jason Snyder <jmssny...@ucdavis.edu> > wrote: > >>> > >>> To Whom It May Concern, > >>> > >>> I am not sure how to handle the namelist.input when running wrf chem as > it does not specify anything in the WRF chem users guide. I noticed I have > several namelist! files in em, namelist.input and namelist.input.fire. I > tried merging the namelist.input.chem with namelist.input by copying all the > chem components of namelist.input.chem into namelist.input and got the > following error message: > >>> > >>> ------ ERROR while reading namelist chem ------ > >>> chem is not a valid namelist name > >>> Namelist dfi_control not found in namelist.input. Using registry > defaults for variables in dfi_control > >>> Namelist tc not found in namelist.input. Using registry defaults for > variables in tc > >>> Namelist scm not found in namelist.input. Using registry defaults for > variables in scm > >>> Namelist fire not found in namelist.input. Using registry defaults for > variables in fire > >>> -------------- FATAL CALLED --------------- > >>> FATAL CALLED FROM FILE: <stdin> LINE: 9104 > >>> ERRORS while reading one or more namelists from namelist.input. > >>> > >>> What does this me! an. amelist.input file(s) so that I can model dust > lofting and transport via the WRF model. I looked at a presentation from > George Grell > >>> > >>> Overview of the WRF/Chem > >>> modeling system > >>> > >>> and he discussed how the GOCART module calculates dust as a function of > the erodible soil area, porosity of soil and also a function of wind speed. > Where do I get erodible soil data? Also do I have to use wrf_prep_chem > program after downloading such data so that it can be used by the WRF > model? I read one article that discussed using TOMS data aerosol indices > for such data. Is that how I should approach things? Could you please > clarify how to handle the namelist. input files in WRF chem and what types > of data I need and how to incorporate this data into the WRF model when > modeling dust lofting and deposition in the WRF model, whether through using > the GOCART m! odule or nbsp; > >>> > >>> > >>> Thanks, > >>> > >>> Jason > >> > >> > > > > > > _______________________________________________ > > vox-tech mailing list > > vox-tech@lists.lugod.org > > http://lists.lugod.org/mailman/listinfo/vox-tech > > > _______________________________________________ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech >
_______________________________________________ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
