public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Martin Steigerwald <ms@teamix.de>
Cc: util-linux-ng@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Support for CFS SCHED_IDLE priority in chrt
Date: Tue, 23 Sep 2008 23:39:13 +0200	[thread overview]
Message-ID: <20080923213913.GP28147@nb.net.home> (raw)
In-Reply-To: <200809231435.54985.ms@teamix.de>

On Tue, Sep 23, 2008 at 02:35:49PM +0200, Martin Steigerwald wrote:
> ms@mango> autoconf      ~/lokal/Kernel/Dokumentation/util-linux-ng
> configure.ac:7: error: possibly undefined macro: AM_INIT_AUTOMAKE
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
> configure.ac:37: error: possibly undefined macro: AM_CONDITIONAL
> configure.ac:190: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION
> configure.ac:191: error: possibly undefined macro: AM_GNU_GETTEXT
> ms@mango> ./configure      ~/lokal/Kernel/Dokumentation/util-linux-ng
> configure: error: cannot find install-sh or install.sh in config "."/config
> 
> when trying to compile util-linux-ng from GIT. (Note: I have no glue about 
> autoconf, I only ever started an pre-existing ./configure script). I tried 
> with autoconf 2.61-8 from Debian Lenny.

 ./autogen.sh
 
> I will test this commit if someone gives me a hint on how to compile 
> util-linux-ng.

 see README.devel


 Applied with minor changes, thanks.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>

  reply	other threads:[~2008-09-23 21:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 12:35 [PATCH] Support for CFS SCHED_IDLE priority in chrt Martin Steigerwald
2008-09-23 21:39 ` Karel Zak [this message]
2008-09-24  7:13   ` Martin Steigerwald
2008-09-24  7:42     ` Karel Zak

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=20080923213913.GP28147@nb.net.home \
    --to=kzak@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@teamix.de \
    --cc=util-linux-ng@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