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

20020506: building udunits: errno.h: No such file or directory

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: 20020506: building udunits: errno.h: No such file or directory
  • Date: Mon, 06 May 2002 13:50:45 -0600
Sally,

> To: address@hidden
> From: Sally Holl <address@hidden>
> Subject: udunits-1.11.7 make errors
> Organization: UCAR/Unidata
> Keywords: 200205061722.g46HMva21483

The above message (and followup message) contained the following:

> I am receiving errors during the make process of installing the
> udunits-1.11.7 package. Here is the requested information:
> 
> $ uname -a
> Linux water 2.4.1 #1 SMP Thu Feb 15 16:57:13 EST 2001 alpha unknown
> 
> Version: udunits-1.11.7
> 
> path of c compiler:
> /usr/bin/gcc
...

> $ make > make.log
> 
> In file included from /usr/include/errno.h:36,
>                  from utlib.c:21: /usr/include/bits/errno.h:25:
> /usr/src/linux-2.4.14/include/asm-alpha/errno.h: No such file or directory
> make[1]: *** [utlib.o] Error 1
> make: *** [lib/all] Error 1

> Thank you for any advice you might have,
> Sally Holl

The error messages above indicate a problem with your C compilation
environment. The file "lib/utlib.c" includes the standard
header-file <errno.h>, which, apparently, includes the header-file
"/usr/src/linux-2.4.14/include/asm-alpha/errno.h", which is not on
your system. The fact that a standard header-file for your C compiler
attempts to include a header-file that doesn't exists indicates a
severe problem with your C development environment. Unfortunately, we
don't have the resources necessary to solve such problems.

I suggest that you show the above error message to your system
administrator or someone else who knows your environment.

Good luck.

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