X11R5 Summary, Xview3 question, xinit question

From: Michael (M.A.) Meystel (MEYSTMA@DUVM.OCS.DREXEL.EDU)
Date: Fri Feb 21 1992 - 00:01:50 CST

This summary is being posted at the request of manderso@mitre.org

My original question regarding X11R5 was about getting a better window
manager than twm, and having something nicer than xterm to talk to the
machine (Sun IPX). What I failed to mention was that I also couldn't
figure out how to exit the windowing system (not the window _manager_,
but the windowing system itself) without rebooting the machine.

It turns out from talking on the phone and e-mail messages, that
twm is a compact, efficient, speedy window manager and is really the
best thing available for pure X windows. The raw twm that I encountered
was horrid, it seems, because I hadn't configured the .twmrc file to
get all the interesting options going. I assume that a site administrator
should do that (silly me) and then make a standard .twmrc file for all the

It has also been mentioned that the OpenLook window manager, olwm, can
be run under X11R5 if Xview3 (from the contrib distribution) is made and
installed. I received 24 answers to my question, some of which contained
sample .twmrc files (thank you!!! and more samples from others would be
welcome!), and most of the replies pointed to xview3 as the answer to my
prayers. Here is where my next question comes in:

First of all, for some reason everything in the contrib directory seems
to think that it's in the X11R5/contrib directory, but when I untarred the
distribution, it placed itself into the X11R5/contrib/contrib directory
(with other stuff like clients and demos and games in the X11R5/contrib
directory). That aside, I started making Xview3 and everything was fine
until I did a "make Clients" command (per the README). If those of you
who have had experience making xview3 could respond to this, I would
appreciate. I got the following error:

cc -o olwmslave cmdstream.o help_file.o helprecv.o helpwin.o mem.o
olwmslave.o propsrecv.o propswin.o -O -pipe -L/usr/lib -lxview -L/usr/lib
-lolgx -lXext -lX11
ld: Undefined symbol
*** Error code 2
make: Fatal error: Command failed for target `olwmslave'
Current working directory
*** Error code 1
make: Fatal error: Command failed for target `all'
Current working directory
*** Error code 1
make: Fatal error: Command failed for target `all'
Current working directory /users/meystel/X11R5/contrib/contrib/lib/xview3
*** Error code 1
make: Fatal error: Command failed for target `Clients'

What can you make of this? Where are those things that it can't find?
What do I need to do to get olwm compiled successfully?

The third question does not concern X11R5, but concerns Sun's OpenWindows
environment. For some reason, every so often (quite frequently recently)
I run into the following console error:

Window display lock brocken as process <PID> blocked

where <PID> points to the process identifier of
/usr/openwin/bin/xinit -- /usr/openwin/bin/xnews :0 -auth ..., etc.
/usr/openwin/bin/xnews :0 -auth ..., etc.

What blocks the window display lock? What is a window display lock? Is this
a bug in the operating system? I have heard of others in our organization
complaining of seeing such messages, but no one has a clear idea of what
causes this.

Thank you.




Michael A. Meystel
IMPAQT Centre Operations
Drexel University Philadelphia PA U.S.A.
(215) 895-5807 / meystma@duvm.ocs.drexel.edu / meystel@impaqt.drexel.edu

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:36 CDT