From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Timothy Miller <tsm@cs.brown.edu>, zsh-workers@sunsite.dk
Subject: Re: zsh 4.0.1 make check failures on irix, freebsd, solaris, aix, linux
Date: Sat, 9 Jun 2001 04:59:24 +0000 [thread overview]
Message-ID: <1010609045924.ZM6260@candle.brasslantern.com> (raw)
In-Reply-To: <yehd78epir3.fsf@water.cs.brown.edu>
Thanks for the feedback, Tim ...
On Jun 8, 9:03pm, Timothy Miller wrote:
}
} I seem to be getting make check failures on the new version of zsh on all
} the architectures we have around here!
The failures in Y03 are a known problem that occurred as a result of a
last-minute patch for a different problem. A fix has been applied to the
CVS repository at SourceForge <https://sourceforge.net/cvs/?group_id=4068>.
You will probably want to "cvs -d ... co -r zsh-4_0-patches".
} On Irix 6.3, gcc 2.8.0, C02, Y01, Y02, Y03 fail. Y0[123] appear to be due to
} zpty failure, which is documented as a lack of support, so I don't include
} them (just C02). Using the SGI cc gives essentially the same result.
The -N test is known to fail on NFS filesystems. Is your build dir NFS'd?
} On Irix 6.5, gcc 2.91.66, again fails C02
} On Solaris 2.7 (Sunos 5.7), gcc 2.95.3, C02
Test ./C02cond.ztst failed: bad status 1, expected 0 from:
[[ -g modish && ! -g zerolength ]]
I tend to think this is NFS-related as well; the test is initialized by
trying to chmod a directory for set-group-id. Depending on the NFS
mount options and whether the current user's default group exists on
the remote server, that might not be possible.
} On RedHat 7.0 linux 2.2.16 gcc 2.96 20000731, C02
Test ./C02cond.ztst failed: bad status 1, expected 0 from:
if ! grep '#define HAVE_FIFOS' $ZTST_testdir/../config.h; then
print -u8 'Warning: Not testing [[ -p pipe ]] (FIFOs not supported)'
[[ ! -p zerolength ]]
else
if whence mkfifo && mkfifo pipe || mknod pipe p; then
[[ -p pipe && ! -p zerolength ]]
else
print -u8 'Warning: Not testing [[ -p pipe ]] (cannot create FIFO)'
[[ ! -p zerolength ]]
fi
fi
I suspect NFS again, particularly if one of the SGI machines is your NFS
server. I wouldn't expect a FIFO created on an NFS filesystem to work
properly (though it should when both client and server are Linux).
} On aix 4.3.2, gcc 2.91.66 fails completely, installed zsh has an error being
} unable to find libzsh-...
Yes, we're just having a discussion about that. Unfortunately none of
the developers has direct access to an AIX machine.
} determined that the link line for both gcc and cc lacks -L to tell it where
} to find libzsh-... Adding that manually produced a zsh which ran and
} immediately segfaulted (even with -f).
The -L information is helpful, thanks (in fact, if you could post a short
manual excerpt relating to it that might be helpful too).
} I then tried the system cc, with
} configure --disable-dynamic and all modules set to link=static in
} config.modules, and that finally ran, but failed A04 and C02
This one (A04) is a race condition in the test and does not represent
an actual failure:
! foo: doo be doo be doo
! bar: doo be doo be doo
--- 1,2 ----
! foo:
! bar:
Test ./A04redirect.ztst failed: output differs from expected as shown above
for:
print "foo: $(<foo)\nbar: $(<bar)"
Was testing: read 2-file multio
The C02 failure is the -g one already discussed above. If NFS is not
involved, please try running:
mkdir modish
chmod g+xs modish
ls -l modish
and see whether `modish' appears to have its setgid bit set.
} but, surprisingly, not Y03.
That is surprising. My guess is it never got tried.
--
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
next prev parent reply other threads:[~2001-06-09 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 1:03 Timothy Miller
2001-06-09 4:59 ` Bart Schaefer [this message]
2001-06-09 16:12 ` Timothy Miller
2001-06-09 17:21 ` Bart Schaefer
2001-06-09 18:01 ` Andrej Borsenkow
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=1010609045924.ZM6260@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=tsm@cs.brown.edu \
--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).