discuss-gnu-electric
[Top][All Lists]
Advanced

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

Re: no display problem


From: Steven Rubin
Subject: Re: no display problem
Date: Thu, 01 Mar 2001 19:29:45 -0800

I just found electric-6.02, and decided to try it on my Linux
Mandrake 7.1, Pentium II machine (actually two of those).

The behavior is the same for both machines.

In a subdirectory of my home directory (as ordinary user)
I do the following (in an X windows terminal screen)

1)  I run ./configure
2)  I modify the generated Makefile as shown below


############################################### X WIDGET SELECTION ############
##### If using Motif/Lesstif widgets, uncomment the next two lines
# TIFFLAGS = -DUSETIF
# XTLIBS = -lXm -lXmu -lXt

##### If using Athena widgets, uncomment the next line
XTLIBS = -lXaw -lXmu -lXt
###############################################################################

to indicate I have the Athena widgets installed.

3) I run make

make terminates normally, and I find the electric executable in the build
directory as promised.

4) I type ./electric in an X windows  terminal screen expecting the
electric display to appear, but I see nothing, not even any error messages
such as "cannot open display",  "cannot find ...", or whatever.

 The README says

"Once compiled, Electric will run properly from the directory where it was
built".

but this does not seem to be happening for me."quit" in the terminal
screen has no effect, and only "^C" kills the process from the keyboard.

5)  After starting electric, I run top, and it tells me that electric is
running (in fact using 50% of the CPU cycles).

Any suggestions would be appreciated.

My first suggestion is to use the LessTif/Motif packages. They are better supported than Athena. However, this problem that you are describing is not necessarily caused by Athena widgets. I have not heard of this problem before, but it might have to do with monitor arrangement. When Electric is using 50% of the CPU time, does it do that for long, or does it quiesce after a minute or two? If it is in a loop, then try running it in the debugger and see if you can get a stack trace to find out where it is spending its time.

   -Steven Rubin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]