[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #WRY-275628]: Installing McIDAS-X without ADDE

Hi Kwan,

> I removed all non-McIDAS env variable in .cshrc (after saving the original).  
> The
> compilation was indeed able to proceed!!

Very good. This, at least, shows that the assumption of something in the
environment being contradictory/confusing to the zlib portion of the McIDAS
build was correct.

> But as it got to mnmx.for, it failed.  I am
> attaching the new .cshrc and the makelog files.

Hmm... this is a problem with your g77 compiler, not with the module mnmx.for:

g77 -c -O -Wuninitialized -fno-automatic -ff90-intrinsics-hide -fno-f2c -g -I. 
etcdf/libsrc -I../hdf/hdf/src -I../hdf/mfhdf/libsrc -I../jpeg -I../libpng 
-I../zlib -
I../tiff/libtiff -I../libgeotiff -I../jasper/src/libjasper/include -I../g2clib 
zip2 mnmx.f
mnmx.f: In function `mnmx':
In file included from mnmx.f:0:
mnmx.f:108: internal compiler error: in gen_reg_rtx, at emit-rtl.c:819
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.

Unfortunately, there is really nothing I can do about internal compiler 

The "solution" to this may well be to use the 'gfortran' compiler instead
of 'g77', OR it might be to install and use a newer version of 'g77' if
such a thing exists.


I ran into a similar problem with gfortran v4.5.1 not being able to generate
an object file from route.pgm on my 64-bit Fedora 14 workstation (there was no
problem under 32-bit Fedora 14!).  I submitted a full bug report in the way 
in the bugzilla link above, and eventually got a status update/close that noted 
particular problem is fixed in gfortran v4.6.  It is this experience that 
that a newer version of 'g77' may not experience the problem you are running 
with the version you are using.


I did a 'grep -i mnmx' for all source files in the McIDAS distribution, and
it looks like the function is not called by any other routines (igtv.pgm
has a call to MNMX, but it also has its own copy of the function, so
it wouldnt't try to use the version that is added to the McIDAS library,
libmcidas.a).  Given this, you could create mnmx.o and continue your build:

<in the mcidas2009/src directory after the error creating mnmx.o>
touch mnmx.o

NB: Given that your version of g77 ran into a problem with mnmx.for (code
that has not been touched since 1997!), it may have similar problems with
other source modules.


Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: WRY-275628
Department: Support McIDAS
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.