[McIDAS #LDE-412096] 20070302: missing modules when make(ing) all

>From: HansPeter Roesli <address@hidden>
>Organization: EUMETSAT
>Keywords: 200703020946.l229k4c7022585 McIDAS build X Windows development

Hi again HP,

re:
>Sorry, if you get this email twice (with slightly different wording, 
>though). I did yesterday's email with a webmailer, the message of which 
>might not pass IT security. Having re-established my Thunderbird now I 
>send it again.

I got your message yesterday and sent a reply.  Did you get the reply?

>vipw worked fine. There is a little variation to the building guide as 
>concerns the shell configuration file. SUSE bash names it bashrc. and 
>not .bash_profile as hinted in the guide. So, up to here no problem.

The answer I provided yesterday was to the effect that the shell
configuration file used for different shells varies somewhat by
operating system.  My examples represent the set of machines we have
here in Unidata that I can test on.  I rely on users being able to
transliterate the User Guide instructions to match their own systems.

>However, when make(ing) all compilation encounters missing modules (of 
>X11 type?). I have been trying to locate them with YaST, but witout 
>succes so far. Any idea how mend y installation?

The makelog output you provide shows that your installation is lacking
the X window development portion.  Since we do not have any experience
in using YaST, we can not be of any direct help.  I did some web
surfing and found an interesting site that might have information of
use:

http://www.suse.de/~sh/YaST2-Package-Manager/

Partway down, I see an interesting comment about displaying all
available packages:

  Improved RPM Groups View
  
  When you select a higher-level RPM group, you now immediately see all
  packages in that category:  A click on Development now immediately
  shows all packages for development. Of course you can still refine that
  by selecting a subcategory like Libraries or C and C++ - but you no
  longer have to.
  
  In addition to that, there is a special entry zzz All (all the way down
  the group tag tree) that displays all available packages.

It might be that YaST2 has everything you need to list development
packages AND download and install them. I would test out this thought
if I had access to a SuSE machine, but, unfortunately, I don't.

>from the warmest winter ever (since 1753 at least), HP

This is a scary comment! I was in The Netherlands at the beginning of
December and I was told that it was some 14C above normal.
Interestingly, the weather here in Colorado is the snowiest it has been
in the past decade (the length of time that I have lived in my current
house) -- and I'm loving the snow!

relevant makelog output

>./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../j
> peg -I../zlib -I../tiff/libtiff -I../libgeotiff enh24.c
>enh24.c:9:22: error: X11/Xlib.h: No such file or directory
>enh24.c:10:23: error: X11/Xutil.h: No such file or directory
>enh24.c:11:21: error: X11/Xos.h: No such file or directory
>enh24.c:12:23: error: X11/Xatom.h: No such file or directory
>enh24.c:14:24: error: X11/keysym.h: No such file or directory
>enh24.c:17:19: error: X11/X.h: No such file or directory
>enh24.c: In function â??enh24_â??:
>enh24.c:24: error: â??Displayâ?? undeclared (first use in this function)
>enh24.c:24: error: (Each undeclared identifier is reported only once
>enh24.c:24: error: for each function it appears in.)
>enh24.c:24: error: â??displayidâ?? undeclared (first use in this function)
>enh24.c:26: error: â??XEventâ?? undeclared (first use in this function)
>enh24.c:26: error: expected â??;â?? before â??reportâ??
>enh24.c:50: error: â??reportâ?? undeclared (first use in this function)
>compile        enh24.c:                FAILED

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.