From: Hrvoje.Niksic@public.srce.hr (Hrvoje Niksic)
To: zsh-workers@math.gatech.edu (zsh)
Subject: Compilation on Ultrix cc
Date: Tue, 7 May 1996 00:54:40 +0200 (MET DST) [thread overview]
Message-ID: <199605062254.AAA09143@jagor.srce.hr> (raw)
I had problems compiling zsh on Ultrix 4.2 with cc.
1. configure determined that the compiler is non-ANSI, which is true enough,
but ansi2knr is still unnecessary since all it does is converting the
function declarations to ANSI-style, and the cc can handle them.
2. In several places the name of a variable is the same as the name of a cpp
macro. The newer cpp-s ignore the variable, whereas the Ultrix cpp gives a
warning, but still makes the substitution with an empty argument. This
prevents the compilation of builtin.c (because of iword macro/variables) and
zle_tricky.c (because of nonempty macro/variables). The solution is to
rename either the macro or the variables in both cases. Note that
zle_tricky.c uses both forms of nonempty.
3. glob.c contains the things that make Ultrix compiler happy wrapped within
#ifdef ULTRIX. However, the Ultrix cc defines only ultrix (lower-case),
which is why a %s/ULTRIX/ultrix is welcome in glob.c. Without it, glob.c
will not compile.
These things done, the shell compiles and works well.
--
hniksic@srce.hr | Student of electrical engineering
hniksic@fly.cc.fer.hr | University of Zagreb, Croatia
------------------------------------------------------------------
`VI' - An editor used by those heretics that don't subscribe to
the Emacs religion.
next reply other threads:[~1996-05-07 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-06 22:54 Hrvoje Niksic [this message]
1996-05-07 1:23 ` Zoltan Hidvegi
[not found] <199605070206.EAA26805@jagor.srce.hr>
1996-05-07 20:39 ` Zoltan Hidvegi
1996-05-08 14:54 ` Zefram
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=199605062254.AAA09143@jagor.srce.hr \
--to=hrvoje.niksic@public.srce.hr \
--cc=hniksic@public.srce.hr \
--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).