2005 00:13:31 -0500
: From: Christopher Faylor <[EMAIL PROTECTED]>
: To: cygwin@cygwin.com
: Subject: Re: P.S. cygheap base mismatch
: Reply-To: cygwin@cygwin.com
: In-Reply-To: <[EMAIL PROTECTED]>
: User-Agent: Mutt/1.5.11
:
: On Wed, Nov 23, 2005 at 01:59:37PM -0800, Lester Ingber wro
On Wed, Nov 23, 2005 at 01:59:37PM -0800, Lester Ingber wrote:
>I have use tcsh scripts run from a Cygwin window to start X-windows. I had
>been using lines like:
>#!/bintcsh -f
>xterm -j -sb -bg white -fg darkblue -cr green -ms magenta -bd red -geometry
>80x84-0+0 -name right >>& /tmp/log.xwin &
esents some problems when using `gcc -mno-cygwin`.
Thanks.
Lester
On Tue, Nov 22, 2005 at 10:43:48PM -0500, Christopher Faylor wrote:
: Date: Tue, 22 Nov 2005 22:43:48 -0500
: From: Christopher Faylor <[EMAIL PROTECTED]>
: To: cygwin@cygwin.com
: Subject: Re: P.S. cygheap base mismatch
: Reply-To:
Lester Ingber wrote:
As I explained in my first posting in this thread, popen() hangs
my code when using the -mn=no-cygwin option under gcc.
Most of the time this happens, I also get printed to STDOUT,
The process tried to write to a nonexistent pipe.
The xterm window in which I am running the
On Tue, Nov 22, 2005 at 07:27:03PM -0800, Lester Ingber wrote:
>Yes, I just put in cygwin1-20051117.dll.
>
>The cygheap problem does not seem to be present, and I'm able to start
>xterm windows. A quirk though: Each xterm window also brings up a
>separate DOS window, and thexterm window is killed
As I explained in my first posting in this thread, popen() hangs
my code when using the -mn=no-cygwin option under gcc.
Most of the time this happens, I also get printed to STDOUT,
The process tried to write to a nonexistent pipe.
The xterm window in which I am running the code freezes, and I ha
Yes, I just put in cygwin1-20051117.dll.
The cygheap problem does not seem to be present, and I'm able to start
xterm windows. A quirk though: Each xterm window also brings up a
separate DOS window, and thexterm window is killed if I kill the DOS
window?
Thanks.
Lester
: You may want to try a
On 11/22/2005, Lester Ingber wrote:
After sending the reply below, I did what I said I did before today
(actually twice) to try to solve this problem: I rebooted my Thinkpad the
way I usually do, by shutting down all running windows (including daemons
like sshd running under Cygwin). I still se
After sending the reply below, I did what I said I did before today
(actually twice) to try to solve this problem: I rebooted my Thinkpad
the way I usually do, by shutting down all running windows (including
daemons like sshd running under Cygwin). I still see:
--8<-- top cut
Larry:
Yes I did stop sshd every time I exited Cygwin, before trying the
various (re-)installations. Why does it seem to you that I haven't?
Note that sshd was likely on when I ran cygcheck under Cygwin.
Lester
On Tue, Nov 22, 2005 at 08:36:24PM -0500, Larry Hall (Cygwin) wrote:
:
: Lester In
Lester Ingber wrote:
I also had reinstalled the most current versions of
cygutils 1.2.9.-1
cygwin 1.5.18.1
I guess there is something else I should try to reinstall as well?
Perhaps my reverting to
mingw-runtime 3.8-1
and then putting back
mingw-runtime 3.9-1
messed up some other DLLs?
You ap
I also had reinstalled the most current versions of
cygutils 1.2.9.-1
cygwin 1.5.18.1
I guess there is something else I should try to reinstall as well?
Perhaps my reverting to
mingw-runtime 3.8-1
and then putting back
mingw-runtime 3.9-1
messed up some other DLLs?
Lester
--
Unsubscribe info:
12 matches
Mail list logo
