zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Vin Shelton <acs@alumni.princeton.edu>,
	zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Failing make check
Date: Mon, 3 Jul 2000 18:01:43 +0000	[thread overview]
Message-ID: <1000703180143.ZM2794@candle.brasslantern.com> (raw)
In-Reply-To: <m2d7kv2k5e.fsf@zion.rcn.com>

On Jul 3,  1:33pm, Vin Shelton wrote:
} Subject: Failing make check
}
} I build my zsh in a separate directory from the sources [...]

So do I.

} For a few days now, make check has been failing in this configuration
} as follows:
} 
} comptestinit:5: failed to load module: zsh/zpty
} comptestinit:18: command not found: zpty
} comptestinit:20: command not found: zpty
} Test /usr/local/src/zsh-2000-07-03/Test/53completion.ztst failed: non-zero status from preparation code:
}   comptestinit -z $ZTST_testdir/../Src/zsh

This is working fine for me.

The first question is, are you sure you're building a dynamically-linked
shell?  The zpty module is not included by default in static builds.

At the very beginning of the test process, you should have seen something
like:

if test -n "gcc"; then \
  cd .. && \
  make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
fi
mkdir /usr/local/build/zsh-2000-07-03/Test/Modules
mkdir /usr/local/build/zsh-2000-07-03/Test/Modules/zsh

This is copying the modules into a local directory at which module_path
is later pointed, to be sure the right modules are loaded.  If you don't
see that install step, you have a statically-linked shell.  If that step
is failing, perhaps because there's a stray Test/Modules directory with
the wrong permissions, then the tests could fail in unpredictable ways.

If that doesn't seem related to the problem, you could try

	ZTST_verbose=2 make TESTNUM=53 check

to see if that reveals anything; but I suspect you're going to have to put
a `set -x' into the prep section of Test/53completion.ztst to get the real
scoop.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-07-03 18:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-03 17:33 Vin Shelton
2000-07-03 18:01 ` Bart Schaefer [this message]
2000-07-04  3:23   ` Vin Shelton
2000-07-04 17:57     ` Vin Shelton

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=1000703180143.ZM2794@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=acs@alumni.princeton.edu \
    --cc=zsh-workers@sunsite.auc.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).