public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Haninger <ahaning@gmail.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Compiling module-init-tools versions after v3.0
Date: Mon, 8 Aug 2005 18:08:57 -0400	[thread overview]
Message-ID: <105c793f050808150810784ef3@mail.gmail.com> (raw)

Hello.

I'm trying to upgrade one of my machines to module-init-tools-3.2-pre8
so that I can better assist a driver developer in debugging some
issues with the OPL3SA2 driver from ALSA.

The machine is currently running a slightly-modified Slackware 9.1
distribution (I've updated several packages to support the 2.6 kernel
and other upgrades since the first install). I currently have
module-init-tools 3.0 installed but I'd like to install version
3.2-pre8.

The problem is that compiling module-init-tools versions after 3.0
seem require docbook-utils (the compile fails on a docbook2man
operation) to be installed and docbook-utils requires jade which will
not compile. I found one jade package called jade-1.2.1 (from '98 or
'99) which will not compile. I tried openjade, but it does not seem to
work when compiling docbook-tools (I made a symlink from the openjade
binary to "jade").

Is there some other package that I'm overlooking that's required to
get docbook-utils installed?  If not, how have other people compiled
and installed newer versions of module-init-tools?

Thanks.

-Andy

             reply	other threads:[~2005-08-08 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 22:08 Andrew Haninger [this message]
2005-08-08 22:32 ` Compiling module-init-tools versions after v3.0 Adrian Bunk
2005-08-09  1:12   ` Andrew Haninger
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=105c793f050808150810784ef3@mail.gmail.com \
    --to=ahaning@gmail.com \
    --cc=linux-kernel@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