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

[McIDAS #HGO-210449]: Shared memory allocation problem in Slackware 10.2

Hi HP,

> vipw worked did the trick.

Its good to know that SuSE Linux includes this standard utility :-)

> A small deviation from the installtion
> guide is that bash in SUSE uses .bashrc (and not .profile_bash or
> similar for configuration.

Yes.  Unfortunately, shell implementations differ on different OSes.
It would be too voluminous to try and list all the various combinations
that a user is likely to see on his/her machine.  I chose, therefore,
to list the ones from systems that we use in-house and hope that users
figure out which files to make the modifications in just like you did.

> So I have come to make all and have hit on a problem that looks like
> missing X11 modules (see attached makelog). 

The makelog entries:

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: 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

indicates either that your machine dies not have a full development environment 
or that the X11 stuff is installed in a different (non-standard) location in 
Linux (this is not likely).

> However, I am not able to
> idenzify with YaST what modules I would have to load. Any idea how to proceed.

Have you looked through the following site for info on how to run YaST:


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

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.

> Cheers from the warmest winter ever, HP

This is a scary comment!  I was in The Netherlands at the beginning of December 
I was told that it was some 14C above normal.  Interestingly, the weather here 
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!

> (the sender of this email might look a bit queer and I hope it does
> pass your system, the reason is that I have to rebuild my emailing
> computer after a heavy disk crash and I am using the web mailer)

I noticed that the From: address was a bit odd (the user name is '103716', but 
address itself is OK:  address@hidden


Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: HGO-210449
Department: Support McIDAS
Priority: Normal
Status: Closed

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.