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

Re: 19990521: Core Dumped on SGI machines?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 19990521: Core Dumped on SGI machines?
  • Date: Fri, 21 May 1999 13:52:51 -0600
Rui,

>Date: Fri, 21 May 1999 15:32:44 -0400
>From: Rui Gong <address@hidden>
>Organization: Boston University
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19990521: Core Dumped on SGI machines?
>Keywords: 199905192123.PAA22412

In the above message, you wrote:

>  I tried as much as possible to follow what you suggested in your last
> email. First I ran 'make distclean', and checked that all '.o' files
> were deleted. Then I ran 'configure'; after which I manually changed
> 'macros.make' to set
> 
> CC              = /bin/c89 -64
> CXX             = /bin/CC -64
> FC              = /bin/f77 -64
> CFLAGS          = -O
> CXXFLAGS        = $(CFLAGS) 
> FFLAGS          = -O
> 
>  After which I did 'make' and 'make test', at which step it failed. I
> appended the unedited log files in the email. Seems like the problems
> are still there.

Manually setting macros in "macros.make" by-passes tests performed by the
configure script.  The script investigates its environment and saves
relevant information in several files.  One of these files is
libsrc/ncconfig.h, which contains things like the size of a C "int".
If the configure script is not executed in a 64-bit environment, then it
will not save that fact in its output configuration files.  The way to
set the environment for the configure script is by setting relevant
environment variables prior to executing the configure script and not
after by manually editing configuration files.

The bottom line is that, unless you know exactly what you are doing, it
is not a good idea to by-pass the configure script by manually editing
output configuration files such as "macros.make".

Please repeat my previous instructions.  When they call for setting
environment variables, please do just that -- and only that -- and do
not subsequently edit any configuration files.

Please let me know if this helps.

--------
Steve Emmerson   <http://www.unidata.ucar.edu>