zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
	<zsh-workers@sunsite.dk>
Subject: RE: 53completion.ztst (Re: zregexparse.ztst fails with latest CVS)
Date: Wed, 7 Feb 2001 10:50:36 +0300	[thread overview]
Message-ID: <000101c090da$a80e3eb0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1010207025802.ZM20171@candle.brasslantern.com>

>
> On Feb 6,  8:23pm, Bart Schaefer wrote:
> } Subject: zregexparse.ztst fails with latest CVS
> }
> } It goes into an infinite loop getting an I/O error on read, according to
> } strace.  This is with the standard default dynamic linkage.
>
> This is on linux, redhat 5.2; sorry for not mentioning it sooner.
>

I cannot reproduce it either on MIPS based Unix. I have CVS + my patch I've
sent at Monday (but it should not affect this anyway). OTOH I cannot run
anything related to zpty for a long time under Cygwin (hoping to look at it
closer). Any chance it may be related?

>
> I noticed that "make clean" doesn't remove the module .so files,

Sorry? You really mean Zsh, do not you? :-)

bor@itsrm2% gmake clean
...
gmake[2]: Entering directory `/u3/u1/build/zsh/Src'
gmake[3]: Entering directory `/u3/u1/build/zsh/Src/Builtins'
rm -f *.o *.export *.so
                         ^^^^
rm -f rlimits.h
rm -f *.o.c *.syms *.pro *.epro *.mdh *.mdhi *.mdhs *.mdh.tmp
gmake[3]: Leaving directory `/u3/u1/build/zsh/Src/Builtins'
gmake[3]: Entering directory `/u3/u1/build/zsh/Src/Modules'
rm -f *.o *.export *.so
                         ^^^^
... etc

-andrej


  parent reply	other threads:[~2001-02-07  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06 20:23 zregexparse.ztst fails with latest CVS Bart Schaefer
2001-02-07  2:58 ` 53completion.ztst (Re: zregexparse.ztst fails with latest CVS) Bart Schaefer
2001-02-07  4:28   ` Vin Shelton
2001-02-07  7:50   ` Andrej Borsenkow [this message]
2001-02-07 17:12     ` Bart Schaefer
2001-02-07 18:23       ` Solved " Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000101c090da$a80e3eb0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=schaefer@candle.brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).