From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: thomas.winder@sea.ericsson.se (Thomas Winder)
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.0.1-test2 compilation problem
Date: Thu, 12 Dec 1996 15:36:49 +0100 (MET) [thread overview]
Message-ID: <199612121436.PAA10835@bolyai.cs.elte.hu> (raw)
In-Reply-To: <ttp3exbhqfh.fsf@stsun46.sea.ericsson.se> from Thomas Winder at "Dec 12, 96 01:56:18 pm"
Thomas Winder wrote:
> Trying to compile zsh-3.0.1-test2 on sparclinux-961210 shows the
> following:
[...]
> builtin.c:3686: #error there are some unknown limits. Fix me!
I compiled zsh on plain RedHad-4.0-sparc which has an old resources.h
that's why I did not notice it. The patch below should fix it. I'm in the
process of replacing SunOS 4 to SparcLinux here and as a test I installed
it on a SUN ELC but that's a lot slower than a 386 DX/40 so I do not have
time to compile the kernel on it, I only use binary kernel images, and I
forgot to upgrage the includes.
That compiles on SparcLinux fine, but it may break something else, so
please test it (especially those using UP-UX-10.20, Digital Unix 4.x or
AIX-4.x).
I know this preprocessor trickery is ugly but the alternatives are not much
better either. We can generate limits with an awk script but it took more
than a year to make the awk script generating signames.h portable. And for
that we have to find out where are the RLIMIT_ macros defined (that seems
to be always in /usr/include/sys/resource.h but on Linux it is under asm).
Zoltan
*** Src/builtin.c 1996/12/11 02:27:28 3.1.0.10
--- Src/builtin.c 1996/12/12 14:08:25
***************
*** 2556,2566 ****
# define NEXT_RLIM (RLIMIT_MEMLOCK + 1)
"memorylocked",
# endif /* RLIMIT_MEMLOCK */
- # if defined RLIMIT_AS && RLIMIT_AS == NEXT_RLIM
- # undef NEXT_RLIM
- # define NEXT_RLIM (RLIMIT_AS + 1)
- "addressspace",
- # endif /* RLIMIT_AS */
# if defined RLIMIT_NPROC && RLIMIT_NPROC == NEXT_RLIM
# undef NEXT_RLIM
# define NEXT_RLIM (RLIMIT_NPROC + 1)
--- 2556,2561 ----
***************
*** 2571,2576 ****
--- 2566,2576 ----
# define NEXT_RLIM (RLIMIT_MEMLOCK + 1)
"memorylocked",
# endif /* RLIMIT_MEMLOCK */
+ # if defined RLIMIT_AS && RLIMIT_AS == NEXT_RLIM
+ # undef NEXT_RLIM
+ # define NEXT_RLIM (RLIMIT_AS + 1)
+ "addressspace",
+ # endif /* RLIMIT_AS */
# if defined RLIMIT_NOFILE && RLIMIT_NOFILE == NEXT_RLIM
# undef NEXT_RLIM
# define NEXT_RLIM (RLIMIT_NOFILE + 1)
next prev parent reply other threads:[~1996-12-12 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-12 12:56 Thomas Winder
1996-12-12 14:36 ` Zoltan Hidvegi [this message]
1996-12-12 17:41 ` Peter Stephenson
1996-12-13 3:24 ` gwing
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=199612121436.PAA10835@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=thomas.winder@sea.ericsson.se \
--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).