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

20050215: Building udunits on Altix IA64 using icc(1): <limits.h>

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: 20050215: Building udunits on Altix IA64 using icc(1): <limits.h>
  • Date: Tue, 15 Feb 2005 10:13:47 -0700
Cliff,

>Date: Tue, 15 Feb 2005 11:58:50 -0500 (EST)
>From: Cliff Liu <address@hidden>
>Organization: NASA
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050215: Building udunits on Altix IA64 using icc(1): <limits.h>

The above message contained the following:

> Yes I did, and I didn't know configure script changes port/misc/limits.h.

The configure(1) script creates whatever files in "port/misc" that it
decides are necessary in order to have a Standard Unix compilation
environment.

> Now we are seeing the errors.
> 
> [root@thunder cliff]# cat conftest.c
> #include "///opt/intel_cc_80/include/limits.h"
> int int_max = INT_MAX;
> [root@thunder cliff]# icc -c conftest.c
> ///opt/intel_cc_80/include/limits.h(22): catastrophic error: could not 
> open source file "limits.h" (no directories in search list)
>    #include_next <limits.h>
>                            ^

Good.  Let's try getting rid of the superfluous slashes in the pathname
of the icc(1) compiler's header-file.  Try this

    echo '#include "/opt/intel_cc_80/include/limits.h"' >conftest.c
    echo 'int int_max = INT_MAX;' >>conftest.c
    icc -c conftest.c

If this fails, then you have a severe problem with your compilation
environment and you might need to consult with the icc(1) vendor.

> Hope we're getting somewhere.

Me too.  Let me know.

Regards,
Steve Emmerson