From: Karel Zak <kzak@redhat.com>
To: Sami Kerola <kerolasa@iki.fi>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 1/2] prlimit: ensure necessary definitions are present
Date: Wed, 26 Oct 2011 23:30:51 +0200 [thread overview]
Message-ID: <20111026213051.GB24870@nb.redhat.com> (raw)
In-Reply-To: <1319482245-5515-1-git-send-email-kerolasa@iki.fi>
On Mon, Oct 24, 2011 at 08:50:44PM +0200, Sami Kerola wrote:
> With Ubuntu linux-libc-dev 2.6.38-11.50 I got error mentioned
> bellow. This patch fixes the issue.
>
> prlimit.c:77:88: error: 'RLIMIT_RTTIME' undeclared here
Good point, but I'm not sure if we want to include kernel header
files (<asm-*/>) to our utils.
I'll fix this issue later (I'm just working on large changes in
configure.in). Thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2011-10-26 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 18:50 [PATCH 1/2] prlimit: ensure necessary definitions are present Sami Kerola
2011-10-24 18:50 ` [PATCH 2/2] build-sys: build prstat only when prlimit() is present Sami Kerola
2011-10-26 21:30 ` Karel Zak [this message]
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=20111026213051.GB24870@nb.redhat.com \
--to=kzak@redhat.com \
--cc=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.org \
/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.
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).