From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Adam Spiers <adam@spiers.net>,
zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: RLIM_NLIMITS compile problem
Date: Wed, 9 Feb 2000 18:02:31 +0000 [thread overview]
Message-ID: <1000209180231.ZM1102@candle.brasslantern.com> (raw)
In-Reply-To: <20000208234852.B25402@thelonious.new.ox.ac.uk>
On Feb 8, 11:48pm, Adam Spiers wrote:
} Subject: RLIM_NLIMITS compile problem
}
} exec.epro:25: `RLIM_NLIMITS' undeclared here (not in a function)
} exec.epro:26: `RLIM_NLIMITS' undeclared here (not in a function)
}
} Not sure whether I'm being stupid or just rusty, but I can't figure
} out where @RLIMITS_INC_H@ is supposed to get #included for this (if
} indeed it is @RLIMITS_INC_H@ - maybe I even got that wrong).
} config.status has:
}
} s%@RLIMITS_INC_H@%/usr/include/asm/resource.h%g
@RLIMITS_INC_H@ is used only in Modules/Makefile.in, whence it comes
via rlimits.mdd.
It appears that zsh expects to get RLIM_NLIMITS (possibly indirectly)
from <sys/resource.h>, which is included by Src/system.h. However, that
depends on HAVE_SYS_RESOURCE_H being defined.
The actual mention of RLIM_NLIMITS in exec.epro began when Zefram put
in the "mod_export" keyword back in December and revised the way that
makepro.awk works. However, I don't see how exec.c itself compiled
before if you're having problems with the .epro now; the trouble appears
to be that HAVE_GETRLIMIT assumes HAVE_SYS_RESOURCE_H, but that must
date from long ago (before I was keeping a CVS repository, at least).
The only other even remotely recent change is that configure.in now
looks at /usr/include/bits/resource.h in addition to all the other
places it used to look, but that's still from last November.
So I'm puzzled, but: Zefram et al., what's the reason that those
HAVE_GETRLIMIT bits in exec.c were never moved to the rlimits module?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-02-09 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 23:48 Adam Spiers
2000-02-09 18:02 ` Bart Schaefer [this message]
2000-02-09 21:43 ` Adam Spiers
2000-02-10 10:02 ` 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=1000209180231.ZM1102@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.auc.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).