Mike Ayers wrote:
[...]
Apparently, run.exe is not providing stdout/stderr to dump to.
Is that by chance due to the fact that run.exe is compiled with -mwindows,
i.e. as GUI?
And am I the only one for whom this has further consequences?
E.g. in a Windows command prompt or a non-X11
Mike Ayers wrote:
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-
ow...@cygwin.com] On Behalf Of Lothar Brendel
Sent: Tuesday, November 10, 2009 4:52 PM
E.g. in a Windows command prompt or a non-X11 cygwin-console, the
command
run sleep -wait 5
does *not* wait for the sleep
Charles Wilson wrote:
[...]
run.exe is peculiar. The first argument is the target, and IF the VERY
NEXT argument is -wait, run usurps that argument. That is, run
will invoke:
checkX other args
and checkX will never see -wait. So, what does run.exe do with
-wait? It...waits. run.exe won't
Charles Wilson wrote:
[...]
The call to XOpenDisplay can take up to 12 seconds. Suppose the main
thread times out after say 5 seconds, and then just after that we
have a *successful* return in the worker thread. The worker thread
tries to get the mutex:
+ (*(data-xclosedis))(dpy);
+
Lothar Brendel wrote:
[...]
The
failure doesn't really harm, but we can be less dirty by checking the
result of pthread_mutex_unlock(), cf. the new patch.
Correction: I meant the result of pthread_mutex_lock() (in open_display()).
Ciao
Lothar
--
Unsubscribe info: http
Charles Wilson wrote:
[...]
AFAICT, the cure for all of these problems is worse than the disease
-- and the only *total* fix is for the main thread to always join()
the worker. Which is precisely what we want to avoid.
ACK and thanx for the explanations.
Ciao
Lothar
--
Unsubscribe
baseball07 wrote:
Hi everyone I am getting this error when I try and locally access the
Linux
machines in my department and try and run a program called Cadence.
Does
anyone know what this means?
Yes, the remote X server can't connect to your local machine, the path to
which is contained in
Charles Wilson wrote:
I've integrated Lothar's patch into run2/checkX (along with some other
internal changes), and published a test release. Please try
run-0.3.1-1 and let me know if it fixes your problems with checkX.
checkX fails due to a missing cygustr-1.dll. That's contained in which
Charles Wilson wrote:
Lothar Brendel wrote:
checkX fails due to a missing cygustr-1.dll. That's contained in
which package?
From http://cygwin.com/packages/ and typing in 'cygustr-1.dll', I get:
Great, thanx for that one.
This *should* have been installed by setup automatically
Charles Wilson wrote:
Lothar Brendel wrote:
It should list, but it doesn't:
$ grep -A9 '@ run2' setup-2.ini
^^^
This was the clue.
As it happens, the union mount stuff had an override for setup.hint,
but not the entire directory. So
Charles Wilson wrote:
Lothar Brendel wrote:
Unfortunately the situatiuon with ``startxwin.bat'' is worse now:
* ``checkX -t 12'' still doesn't wait (?!?)
I can't reproduce this.
Stupid me, sorry. When updating to pull in libustr1, run2 was accidently
reverted to 0.3.0-1.
* After again
Timares, Brian (Patriot) wrote:
[...]
Nothing works. 1.7 doesn't work for me out-of-the-box (yes, I ripped
it all out and tried it fresh :-)
I open a DOS box and check processes and see bash running with an l or
a 1 in the left columnn, but nothing appears. If I launch an Xterm
it opens up.
Thomas Dickey wrote:
On Thu, 26 Nov 2009, Lothar Brendel wrote:
[...]
Hence, to make Cygwin/X+xterm run out of the box (using
the start menu shortcut), you have to install the CJK fonts. One
more noob-question,
otoh, (discarding run-out-of-the-box, since that doesn't give a good
solution
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
[...]
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me, that's
the default version. But we need 0.3.1-1, which you only get when
explicitely (triple
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
My guess: It's the old checkX-problem again because you're using
version
0.3.0-1 of the run2-package. Do to some reason unknown to me,
that's the default version. But we need 0.3.1-1
Timares, Brian (Patriot) wrote:
Just to be clear from the start, Cygwin 1.7 not 1.5.
ACK.
[...]
i) ```time checkX -t 12''
How long does it take?
vhaisbtim...@isb-timaresbrian-lt ~
$ time checkX -t 12
real0m0.098s
user0m0.046s
sys 0m0.031s
And *that* shouldn't happen!
I
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
[...]
Thus, once more: What does
md5sum /usr/bin/checkX
yield?
a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216?
The 2nd:
vhaisbtim...@isb-timaresbrian-lt ~
$ md5sum /usr/bin/checkX
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
Timares, Brian (Patriot) wrote:
Lothar Brendel wrote:
$ checkX -v
run2 0.3.0
So, you've got the situation I surmised in
http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html
Grr, I saw that, went and _thought_ I got the right version
Hi!
More information as promised, after getting the new run and checkX
(run2) packages announced this morning.
$ checkX -v
run2 0.3.2
0.3.2 announced? I didn't get any such message, and setup still only offers
0.3.1-1 to me.
vhaisbtim...@isb-timaresbrian-lt ~
$ XWin -multiwindow
[1]
Christopher Faylor wrote:
On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote:
More information as promised, after getting the new run and checkX
(run2) packages announced this morning.
$ checkX -v
run2 0.3.2
0.3.2 announced? I didn't get any such message, and setup still only
20 matches
Mail list logo
