[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20050120: McIDAS-X build (cont.)
- Subject: 20050120: McIDAS-X build (cont.)
- Date: Thu, 20 Jan 2005 17:32:37 -0700
>From: "Luis A. Lopez" <address@hidden>
>Organization: UPRM
>Keywords: 200501201240.j0KCevv2003384 McIDAS build
Hi Luis,
> I found the error in mcinstall. It is in line 52
>
> echo You must define McINST_ROOT as the full pathname of an"
>
>a " is missed after the echo.
Hmm... I just looked at the copy sitting in the FTP directory for
Unidata McIDAS, and it is not missing the " after the echo. The
next character after the echo is a CTRL-G (bell), so that may be
causing the problem for some reason (it doesn't on other Linux systems).
>Now I'm getting this error
>
>./mccomp -O -g77 -I. -I../netcdf/libsrc -I../hdf/hdf/src -
>I../hdf/mfhdf/libsrc -I../jpeg -I../zlib -I
>../tiff/libtiff -I../libgeotiff -c enh24.c
>mccomp: Using default optimizations
>rm -f enh24.o
>gcc -c -O -I. -I../netcdf/libsrc -I../hdf/hdf/src -I../hdf/mfhdf/libsrc -
>I../jpeg -I../zlib -I../tiff
>/libtiff -I../libgeotiff enh24.c
>enh24.c:9:22: X11/Xlib.h: No such file or directory
>enh24.c:10:23: X11/Xutil.h: No such file or directory
>enh24.c:11:21: X11/Xos.h: No such file or directory
>enh24.c:12:23: X11/Xatom.h: No such file or directory
>enh24.c:14:24: X11/keysym.h: No such file or directory
>enh24.c:17:19: X11/X.h: No such file or directory
>enh24.c: In function `enh24_':
>enh24.c:24: `Display' undeclared (first use in this function)
>enh24.c:24: (Each undeclared identifier is reported only once
>enh24.c:24: for each function it appears in.)
>enh24.c:24: `displayid' undeclared (first use in this function)
>enh24.c:26: `XEvent' undeclared (first use in this function)
>enh24.c:26: syntax error before "report"
>enh24.c:50: `report' undeclared (first use in this function)
>compile enh24.c: FAILED
>
This is saying that the Linux box does not have a full development
enviornment loaded on it -- the X windows include files are missing.
You should go back and load a full development enviornment on the machine
and then retry the build after doing a 'make clobber'.
Cheers,
Tom
--
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.