From: Andrew Haninger <ahaning@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
"Adam J. Richter" <adam@yggdrasil.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Compiling module-init-tools versions after v3.0
Date: Mon, 8 Aug 2005 21:12:45 -0400 [thread overview]
Message-ID: <105c793f0508081812353a07d3@mail.gmail.com> (raw)
In-Reply-To: <20050808223209.GL4006@stusta.de>
On 8/8/05, Adrian Bunk <bunk@stusta.de> wrote:
> Workaround:
>
> Remove the
>
> man_MANS = $(MAN5) $(MAN8)
>
> line in Makefile.in before running configure.
On 8/8/05, Ken Moffat <ken@kenmoffat.uklinux.net> wrote:
> per LFS (http://www.linuxfromscratch.org/lfs/) make DOCBOOKTOMAN=""
> (or look at BLFS for the gory details of docbook)
Thank you both. Both of those workarounds seem to work for now.
> But this could be better handled in module-init-tools.
Here's hoping it will be once 3.2 is released.
Thanks again.
-Andy
next prev parent reply other threads:[~2005-08-09 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 22:08 Compiling module-init-tools versions after v3.0 Andrew Haninger
2005-08-08 22:32 ` Adrian Bunk
2005-08-09 1:12 ` Andrew Haninger [this message]
2005-08-09 4:30 ` Rusty Russell
2005-08-09 0:25 ` Ken Moffat
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=105c793f0508081812353a07d3@mail.gmail.com \
--to=ahaning@gmail.com \
--cc=adam@yggdrasil.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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