zsh-workers
 help / color / mirror / code / Atom feed
From: Timo Aaltonen <tjaalton@cc.hut.fi>
To: ZSH Workers Mailing List <zsh-workers@sunsite.dk>
Subject: Re: Y03 hangs on AIX
Date: Wed, 27 Jun 2001 16:22:28 +0300 (EET DST)	[thread overview]
Message-ID: <Pine.OSF.4.10.10106271609110.12353-100000@tiku.hut.fi> (raw)
In-Reply-To: <003901c0ff09$fdd95080$21c9ca95@mow.siemens.ru>

On Wed, 27 Jun 2001, Andrej Borsenkow wrote:

> >
> > > >
> > > > It gave me the term.h/boolcodes -error.. maybe terminfo could
> > be left as a
> > > > module?
> > > >
> > >
> > > Ahh ... no, it is the same problem. I just realized, it won't work with
> > > LIBS=-ltermcap as well because we currently prefer
> > term.h/curses.h if they
> > > exist.
> >
> > Actually, I compiled the whole thing with just LIBS=-ltermcap defined,
> > didn't comment out those modules and it passed the compilation...
> 
> Umm ... ashamed :-( anyway, I guessed the correct result :-)
> 
> but make
> > check hung on test Y03...
> >
> 
> I think we had one more report ... could you run
> 
> ZTST_verbose=2 make TESTNUM=Y03 check?

theremin zsh-4.0.2 369 % ZTST_verbose=2 make TESTNUM=Y03 check
        cd Test ; make check
        if test -n "cc -qlanglvl=ansi"; then  cd .. &&  make
MODDIR=`pwd`/Test/Modules install.modules > /dev/null;  fi
    1500-030: (I) INFORMATION: bin_zformat: Additional optimization may be
attained by recompiling and specifying MAXMEM option with a value greater
than 2048.
        for f in ./Y03*.ztst; do  ../Src/zsh +Z -f ./ztst.zsh $f;  done
./Y03arguments.ztst: starting.
ZTST_getsect: read section name: prep
ZTST_getchunk: read code chunk:
  . $ZTST_srcdir/comptest
ZTST_execchunk: status 0
ZTST_getchunk: read code chunk:
  mkdir comp.tmp
  cd comp.tmp
ZTST_execchunk: status 0
ZTST_getchunk: read code chunk:
  comptestinit -z $ZTST_testdir/../Src/zsh
  comptesteval 'compdef _tst tst'
  tst_arguments () { comptesteval "_tst () { _arguments ${${(@qq)*}} }" }
ZTST_execchunk: status 0
ZTST_getchunk: read code chunk:

ZTST_getsect: read section name: test
ZTST_test: looking for new test
ZTST_test: examining line:
 tst_arguments ':desc1:(arg1)'
ZTST_getchunk: read code chunk:
 tst_arguments ':desc1:(arg1)'
 comptest $'tst \t\C-wa\t\C-war\t\C-warg\t\C-warg1\t\C-wr\t\C-wx\t \ty \t'
ZTST_test: examining line:
>line: {tst arg1 }{}
ZTST_getredir: read redir for '>':
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst r}{}
line: {tst x}{}
line: {tst x }{}
MESSAGE:{no more arguments}
line: {tst x y }{}
MESSAGE:{no more arguments}
ZTST_test: examining line:

Running test: one non-option argument
ZTST_test: expecting status: 0
ZTST_execchunk: status 0
ZTST_test: test produced standard output:
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst arg1 }{}
line: {tst r}{}
line: {tst x}{}
line: {tst x }{}
MESSAGE:{no more arguments}
line: {tst x y }{}
MESSAGE:{no more arguments}
ZTST_test: and standard error:

Test successful.
ZTST_test: looking for new test
ZTST_test: examining line:

ZTST_test: examining line:
 tst_arguments ':desc1:(a b)'
ZTST_getchunk: read code chunk:
 tst_arguments ':desc1:(a b)'
 comptest $'tst \t'
ZTST_test: examining line:
>line: {tst }{}
ZTST_getredir: read redir for '>':
line: {tst }{}
DESCRIPTION:{desc1}
NO:{a}
NO:{b}
ZTST_test: examining line:

Running test: a and b
ZTST_test: expecting status: 0

...and that's as far as where it gets =(


> It was 4.0.2 or CVS?

4.0.2


_______________/Timo Aaltonen <http://www.hut.fi/~tjaalton>
Work: HUT-Computing Centre - UNIX,  GSM +358-40-5549 618



  reply	other threads:[~2001-06-27 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.OSF.4.10.10106271554280.12353-100000@tiku.hut.fi>
2001-06-27 13:06 ` Andrej Borsenkow
2001-06-27 13:22   ` Timo Aaltonen [this message]
2001-06-28 13:21   ` Tru64 problems on tests A01 and Y03 (Was Re: Y03 hangs on AIX) Timo Aaltonen

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=Pine.OSF.4.10.10106271609110.12353-100000@tiku.hut.fi \
    --to=tjaalton@cc.hut.fi \
    --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).