* zsh 4.1.1 make check errors on OS X 10.2
@ 2004-01-01 0:34 Culley Harrelson
2004-01-01 1:32 ` zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2] James Devenish
0 siblings, 1 reply; 6+ messages in thread
From: Culley Harrelson @ 2004-01-01 0:34 UTC (permalink / raw)
To: zsh-users
I am new to zsh so I don't know how to do further tests on the below
errors. It installed fine and seems to be working without problems.
With 10.3 out now my environment is getting obscure but I thought I
would post these test results anyway...
culley
=============
culley@localhost ~/Documents/software/zsh-4.1.1
% make check
cd Test ; make check
if test -n ""; then \
cd .. && DESTDIR= \
make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
fi
for f in ./*.ztst; do \
../Src/zsh +Z -f ./ztst.zsh $f; \
done
./A01grammar.ztst: starting.
This test hangs the shell when it fails...
./A01grammar.ztst: all tests successful.
./A02alias.ztst: starting.
./A02alias.ztst: all tests successful.
./A03quoting.ztst: starting.
./A03quoting.ztst: all tests successful.
./A04redirect.ztst: starting.
./A04redirect.ztst: all tests successful.
./A05execution.ztst: starting.
./A05execution.ztst: all tests successful.
./A06assign.ztst: starting.
./A06assign.ztst: all tests successful.
./B01cd.ztst: starting.
./B01cd.ztst: all tests successful.
./B02typeset.ztst: starting.
./B02typeset.ztst: all tests successful.
./B03print.ztst: starting.
./B03print.ztst: all tests successful.
./B04read.ztst: starting.
./B04read.ztst: all tests successful.
./C01arith.ztst: starting.
./C01arith.ztst: all tests successful.
./C02cond.ztst: starting.
Test ./C02cond.ztst failed: bad status 1, expected 0 from:
sleep 1
cat unmodified
touch newnewnew
if [[ $OSTYPE == "cygwin" ]]; then
print -u8 "Warning: not testing [[ -N file ]] (not supported on
Cygwin)"
true
else
[[ -N newnewnew && ! -N unmodified ]]
fi
Was testing: -N cond
./C02cond.ztst: test failed.
The following may (or may not) help identifying the cause:
This test can fail on NFS-mounted filesystems as the access and
modification times are not updated separately. This does not indicate
a problem in the shell.
./C03traps.ztst: starting.
This test takes at least three seconds...
This test, too, takes at least three seconds...
./C03traps.ztst: all tests successful.
./C04funcdef.ztst: starting.
./C04funcdef.ztst: all tests successful.
./D01prompt.ztst: starting.
./D01prompt.ztst: all tests successful.
./D02glob.ztst: starting.
./D02glob.ztst: all tests successful.
./D03procsubst.ztst: starting.
./D03procsubst.ztst: all tests successful.
./D04parameter.ztst: starting.
./D04parameter.ztst: all tests successful.
./D05array.ztst: starting.
./D05array.ztst: all tests successful.
./D06subscript.ztst: starting.
./D06subscript.ztst: all tests successful.
./E01options.ztst: starting.
./E01options.ztst: all tests successful.
./E02xtrace.ztst: starting.
./E02xtrace.ztst: all tests successful.
./V01zmodload.ztst: starting.
Warning: zsh/example not linked: not checking autoloading
./V01zmodload.ztst: all tests successful.
./V02zregexparse.ztst: starting.
./V02zregexparse.ztst: all tests successful.
./Y01completion.ztst: starting.
comptestinit:7: failed to load module: zsh/zpty
Test ./Y01completion.ztst failed: non-zero status from preparation code:
comptestinit -z $ZTST_testdir/../Src/zsh &&
{
mkdir dir1 &&
mkdir dir2 &&
touch file1 &&
touch file2
}
./Y01completion.ztst: test failed.
Test ./Y01completion.ztst failed: bad status 1, expected 0 from:
comptest $': \t\t\t\t\t\t\t'
Error output:
comptest:2: command not found: zpty
comptest:3: command not found: zpty
Was testing: directories and files
./Y01completion.ztst: test failed.
./Y02compmatch.ztst: starting.
comptestinit:7: failed to load module: zsh/zpty
Test ./Y02compmatch.ztst failed: non-zero status from preparation code:
comptestinit -z $ZTST_testdir/../Src/zsh &&
{
list1=(IndianRed IndianRed2 IndianRed3 IndianRed4)
test_code () {
matcher=$1;
list=$2;
code="compdef _tst tst ; _tst () { echo -n '<COMPADD>';compadd
-M '"
code="$code$matcher"
code="$code' - ${(P)list} ; echo -n '</COMPADD>'"
code="$code; $extra_cmd"
code="$code; echo -n '<INSERT_POSITIONS>'"
code="$code; echo \$compstate[insert_positions]"
code="$code; echo -n '</INSERT_POSITIONS>'"
code="$code}"
comptesteval "$code"
}
}
./Y02compmatch.ztst: test failed.
Test ./Y02compmatch.ztst failed: bad status 1, expected 0 from:
test_code z: list1
comptest $'tst \t'
Error output:
(eval):1: command not found: test_code
comptest:2: command not found: zpty
comptest:3: command not found: zpty
Was testing: Match Error for "z:"
./Y02compmatch.ztst: test failed.
./Y03arguments.ztst: starting.
comptestinit:7: failed to load module: zsh/zpty
Test ./Y03arguments.ztst failed: non-zero status from preparation code:
comptestinit -z $ZTST_testdir/../Src/zsh &&
{
comptesteval 'compdef _tst tst'
tst_arguments () { comptesteval "_tst () { _arguments ${${(@qq)*}}
}" }
}
./Y03arguments.ztst: test failed.
Test ./Y03arguments.ztst failed: bad status 1, expected 0 from:
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'
Error output:
(eval):1: command not found: tst_arguments
comptest:2: command not found: zpty
comptest:3: command not found: zpty
Was testing: one non-option argument
./Y03arguments.ztst: test failed.
make[1]: [check] Error 1 (ignored)
rm -rf Modules .zcompdump
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2]
2004-01-01 0:34 zsh 4.1.1 make check errors on OS X 10.2 Culley Harrelson
@ 2004-01-01 1:32 ` James Devenish
2004-01-01 16:10 ` Culley Harrelson
2004-01-08 11:26 ` Oliver Kiddle
0 siblings, 2 replies; 6+ messages in thread
From: James Devenish @ 2004-01-01 1:32 UTC (permalink / raw)
To: zsh-users
Hi,
In message <525FE6E8-3BF2-11D8-B757-000A9591EB8C@fastmail.fm>
on Wed, Dec 31, 2003 at 04:34:55PM -0800, Culley Harrelson wrote:
> I am new to zsh so I don't know how to do further tests on the below
> errors. It installed fine and seems to be working without problems.
> With 10.3 out now my environment is getting obscure but I thought I
> would post these test results anyway...
[...]
> ./C02cond.ztst: starting.
> Test ./C02cond.ztst failed: bad status 1, expected 0 from:
[...]
> Was testing: -N cond
> ./C02cond.ztst: test failed.
This will fail on HFS+ volumes because the access time is not stored (it
will always be equal to the modification time). I suspect there *is* a
dedicated field in the filesystem for storing it (for POSIX purposes)
but it is traditionally absent, and currently unused, under Apple
operating systems. Happily, this would not be a zsh bug per se, so the
following text could be updated:
> The following may (or may not) help identifying the cause:
> This test can fail on NFS-mounted filesystems as the access and
> modification times are not updated separately. This does not indicate
> a problem in the shell.
E.g. "...This test can fail on NFS-mounted or HFS+ (Apple Mac OS X
default) filesystems as the...".
> ./Y01completion.ztst: starting.
> comptestinit:7: failed to load module: zsh/zpty
The remainder of the errors appear to be related to the "failed to load
module: zsh/zpty" problem. I don't appear to have any such problem under
10.3.1.
PS. I get a lot of warnings about "implicit declaration of function
'ioctl'" (because sys/ioctl.h is not included) but of course there is no
problem when linking. Also, I note that object files have names like
blah..o instead of blah.o (not that it matters).
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2]
2004-01-01 1:32 ` zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2] James Devenish
@ 2004-01-01 16:10 ` Culley Harrelson
2004-01-02 2:30 ` James Devenish
2004-01-08 11:26 ` Oliver Kiddle
1 sibling, 1 reply; 6+ messages in thread
From: Culley Harrelson @ 2004-01-01 16:10 UTC (permalink / raw)
To: James Devenish; +Cc: zsh-users
On Wednesday, December 31, 2003, at 05:32 PM, James Devenish wrote:
> The remainder of the errors appear to be related to the "failed to load
> module: zsh/zpty" problem. I don't appear to have any such problem
> under
> 10.3.1.
>
ok. I will be upgrading within the next few months.
Do you have any problems with fancy prompts? I tried to source this
prompt file:
http://aperiodic.net/phil/prompt/prompt.txt
And it is garbled. Many of the builtin prompt themes are also
garbled...
culley
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2]
2004-01-01 16:10 ` Culley Harrelson
@ 2004-01-02 2:30 ` James Devenish
0 siblings, 0 replies; 6+ messages in thread
From: James Devenish @ 2004-01-02 2:30 UTC (permalink / raw)
To: zsh-users
In message <FF6E1D8D-3C74-11D8-B757-000A9591EB8C@fastmail.fm>
on Thu, Jan 01, 2004 at 08:10:20AM -0800, Culley Harrelson wrote:
> Do you have any problems with fancy prompts?
I would consider my personal prompt be very fancy, and I have no
problems with it.
> I tried to source this prompt file:
> http://aperiodic.net/phil/prompt/prompt.txt
Hmm, that is complicated on a similar scale of my own. And, likewise, I
experience no trouble with it under 10.3 (Darwin 7). I did try zsh under
10.2 and it seems that the 'dynamic' modules are not built.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2]
2004-01-01 1:32 ` zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2] James Devenish
2004-01-01 16:10 ` Culley Harrelson
@ 2004-01-08 11:26 ` Oliver Kiddle
2004-01-08 11:27 ` James Devenish
1 sibling, 1 reply; 6+ messages in thread
From: Oliver Kiddle @ 2004-01-08 11:26 UTC (permalink / raw)
To: James Devenish; +Cc: zsh-users
On 1 Jan, James Devenish wrote:
> The remainder of the errors appear to be related to the "failed to load
> module: zsh/zpty" problem. I don't appear to have any such problem under
> 10.3.1.
Have you got the dlcompat library installed? If you look at
Etc/MACHINES it mentions that it is needed.
Is dlcompat still needed under 10.3.1? i.e. have you just got dlcompat
there as part of something like fink or has Apple added native support
for dlopen etc?
> PS. I get a lot of warnings about "implicit declaration of function
> 'ioctl'" (because sys/ioctl.h is not included) but of course there is no
> problem when linking. Also, I note that object files have names like
> blah..o instead of blah.o (not that it matters).
I think that ..o is intentional somewhere for some reason.
Your suggested change for the test's help info sounds sensible.
Oliver
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2]
2004-01-08 11:26 ` Oliver Kiddle
@ 2004-01-08 11:27 ` James Devenish
0 siblings, 0 replies; 6+ messages in thread
From: James Devenish @ 2004-01-08 11:27 UTC (permalink / raw)
To: zsh-users
In message <6972.1073561189@gmcs3.local>
on Thu, Jan 08, 2004 at 12:26:29PM +0100, Oliver Kiddle wrote:
> Have you got the dlcompat library installed?
It took me a while to find a 10.2 machine. I can confirm that it had no
dlcompat. Not sure about the original poster. I did specify the module
to be linked statically and I seem to remember that there were still
difficulties (there was also another condition expression failure). I
have not encountered problems with the same version of zsh on hosts
running 10.3 with fink (and dlcompat) also installed.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-01-08 11:27 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-01 0:34 zsh 4.1.1 make check errors on OS X 10.2 Culley Harrelson
2004-01-01 1:32 ` zsh 4.1.1 make check errors on OS X 10.3 [was: 10.2] James Devenish
2004-01-01 16:10 ` Culley Harrelson
2004-01-02 2:30 ` James Devenish
2004-01-08 11:26 ` Oliver Kiddle
2004-01-08 11:27 ` James Devenish
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).