[Wrf-users] WRFV2.0.3.1 and IFORT 8.1 on an 32-bit i686 (not xeon)

Anthony Toigo toigo at astro.cornell.edu
Wed Feb 9 01:45:56 MST 2005


Hi,

I've also been trying to compile WRFV2.0.3.1 with the ifort v8.1 compiler
on an i686 processor and have been running into some problems myself.

Starting with a fresh copy of the tar file, at this point I am simply
trying to get one of the ideal cases to compile and run as a test.  I have
been working with "em_b_wave" for now.

I have a 32-bit Pentium 3 i686 Fedora Core 3 Linux machine that I am
building and testing this on.  I have the ifort v8.1 compilers, and started
with gcc (3.4.2-6.fc3) but just today acquired the icc v8.1 compiler as
well.  The netCDF version I am using is v3.6.0, and was built with ifort
and gcc.  When compiling, I chose option "7.  Intel xeon i686 ia32 Xeon
Linux, ifort compiler (single-threaded, no nesting)" with no other
modifications or flags (with the one exception of using gcc vs. icc, but
now I have used both and that makes no difference).

The good news is that WRF compiles just fine.  And ideal.exe runs fine to
completion with no errors.  The problem comes with running wrf.exe.  The
code always crashes with a SEGV (segmentation violation) in solve_em.
The exact line (according to the debuggers) is:

1080  history_outname = grid%history_outname

This same error occurs in the exact same place no matter whether I use gcc
or icc, so at least I've ruled that out.

Adding a debug print line, like

write(0,*) 'history_outname=',history_outname

before the Registry-generated assignment statements also causes the code to
crash.  I can't understand why the character*256 variable, or using it in
an assignment statement, or even just printing it, would cause a
segmentation violation, but I would like to know.

Has anyone else experienced this problem?  If anyone has gotten WRF to
compile on a 32-bit i686 machine with Fedora Core 3 or so and the ifort v8.1
compilers, did you run into any problems?  Did you make any changes to the
configure.defaults file to get it to compile and/or run, and if so, what
changes did you make?  Any help anyone can offer would be appreciated.

Thanks,

Anthony Toigo
Cornell University


More information about the Wrf-users mailing list