From: Jukka Virtanen <jtv@cc.hut.fi>
To: zsh-workers@math.gatech.edu
Subject: two bugs in zsh 3.0.1-test3
Date: Tue, 8 Oct 1996 19:41:12 +0300 (EET DST) [thread overview]
Message-ID: <Pine.OSF.3.93.961008193221.6481T-100000@alpha.hut.fi> (raw)
=====================================================================
Bug 1:
If zsh 3.0.1-test3 is compiled in a separate object directory,
the compilation goes ok, but the install fails, because
the info files are not found by the Make. Here is a fix
to this problem:
*** Doc/Makefile.in~ Wed Jul 31 21:41:12 1996
--- Doc/Makefile.in Tue Oct 8 19:25:07 1996
***************
*** 125,131 ****
# install info pages, creating install directory if necessary
install.info: zsh.info
$(top_srcdir)/mkinstalldirs $(infodir)
! for file in zsh.info zsh.info-[1-9]; do \
[ -f "$$file" ] && $(INSTALL_DATA) $$file $(infodir) ; \
done
--- 125,131 ----
# install info pages, creating install directory if necessary
install.info: zsh.info
$(top_srcdir)/mkinstalldirs $(infodir)
! for file in $(srcdir)/zsh.info $(srcdir)/zsh.info-[1-9]; do \
[ -f "$$file" ] && $(INSTALL_DATA) $$file $(infodir) ; \
done
=====================================================================
Bug 2:
In an Alpha host running Digital Unix V4.0:
narya dist 554 % uname -a
OSF1 narya.hut.fi V4.0 386 alpha
The zsh prototypes.h file contains a prototype declaration
for the ioctl routine:
int ioctl _((int d, unsigned long request, void *argp));
The declaration is inconsistent with the vendor supplied
prototype declaration in /usr/include/sys/ioctl.h :
extern int ioctl __((int, int, ...));
I compiled zsh by commenting out the ioctl declaration
from prototypes.h.
Juki
jtv@hut.fi
next reply other threads:[~1996-10-08 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-08 16:41 Jukka Virtanen [this message]
1996-10-08 23:11 ` 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.OSF.3.93.961008193221.6481T-100000@alpha.hut.fi \
--to=jtv@cc.hut.fi \
--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).