From: "C. v. Stuckrad" <stucki@math.fu-berlin.de>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: Zsh hacking and development <zsh-workers@math.gatech.edu>
Subject: Re: zsh-3.0.2-test2
Date: Wed, 11 Dec 1996 13:23:11 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.3.95.961211131151.4840A-100000@petzval> (raw)
In-Reply-To: <199612110303.EAA02736@hzoli.ppp.cs.elte.hu>
On Wed, 11 Dec 1996, Zoltan Hidvegi wrote:
> ftp://ftp.cs.elte.hu/pub/zsh/testing/zsh-3.0.2-test2.diff.gz
Got this...
> It should be applied to the clean zsh-3.0.1 source. The first hunk of the
> FAQ will fail since the patch is generated by RCS.
OK, it did exacly that...
So I let it configure...
Well, NOW something changed !
Up to *-test1 configure dids assume we HAVE FIFOS,
BUT NOW IT SAYS WE HAVE NO(!) FIFOS in the *-test2 !
Its on the same machine (sun-sparc-10) same system (Solaris 2.4)
in the same source-tree (I found it by doing:
1) unpacking *3.0.1.tar.gz
2) then patching
3) configure --enable-etcdir=...
4) DOING: cd ..; diff -b -r -c zsh*-test? | less
I tried to compare with a *3.0.2-test1 generated by unpacking, patching,
configuring, THEN APPLYING THE THREE PATCHES FROM THE LIST, then
reconfiguring. I was intrested how much the tree patches of the list
did differ from the *-test2. AND THEN I WAS SUPRIZED !!!
Any ideas how our FIFOs got lost ?
Stucki
Christoph von Stuckrad * * | talk to | <stucki@math.fu-berlin.de> \
Freie Universitaet Berlin |/_* | nickname | ...!unido!fub!leibniz!stucki|
Fachbereich Mathematik, EDV |\ * | 'stucki' | Tel:+49 30 838-7545{9|8} |
Arnimallee 2-6/14195 Berlin * * | on IRC | Fax:+49 30 838-5913 /
next prev parent reply other threads:[~1996-12-12 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-11 3:03 zsh-3.0.2-test2 Zoltan Hidvegi
1996-12-11 12:23 ` C. v. Stuckrad [this message]
1996-12-11 14:53 ` zsh-3.0.2-test2 Zefram
1996-12-11 21:58 ` zsh-3.0.2-test2 did it again (partly?) C. v. Stuckrad
1996-12-12 1:43 ` Zoltan Hidvegi
1996-12-12 1:45 ` Zoltan Hidvegi
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.GSO.3.95.961211131151.4840A-100000@petzval \
--to=stucki@math.fu-berlin.de \
--cc=hzoli@cs.elte.hu \
--cc=zsh-workers@math.gatech.edu \
/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).