Compiling module-init-tools versions after v3.0

Compiling module-init-tools versions after v3.0

[Andrew Haninger]

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

Re: Compiling module-init-tools versions after v3.0

[Adrian Bunk]

On Mon, Aug 08, 2005 at 06:08:57PM -0400, Andrew Haninger wrote:

> Hello.


Hi Andrew,


> 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?


Workaround:

Remove the

  man_MANS = $(MAN5) $(MAN8)

line in Makefile.in before running configure.


But this could be better handled in module-init-tools.


> Thanks.
> 
> -Andy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: Compiling module-init-tools versions after v3.0

[Ken Moffat]

On Mon, 8 Aug 2005, Andrew Haninger wrote:

>
> 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").
>

 per LFS (http://www.linuxfromscratch.org/lfs/) make DOCBOOKTOMAN=""
(or look at BLFS for the gory details of docbook)

Ken
-- 
 das eine Mal als Tragödie, das andere Mal als Farce

Re: Compiling module-init-tools versions after v3.0

[Andrew Haninger]

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

Re: Compiling module-init-tools versions after v3.0

[Rusty Russell]

On Mon, 2005-08-08 at 21:12 -0400, Andrew Haninger wrote:
> On 8/8/05, Adrian Bunk <bunk@stusta.de> wrote:
> > But this could be better handled in module-init-tools.
> Here's hoping it will be once 3.2 is released.
> 
> Thanks again.
> 
> -Andy

Thanks for this report!  This is the first I've heard of it (Adam CC'd
me, thanks!).

Turns out the "docbook2man" uses the *last* <refentrytitle> as the
output filename, so it was building "modprobe.d.5" instead of
"modprobe.conf.5".  As a result, modprobe.conf.5 was always old, even in
the tarball I uploaded for 3.1 (when the second refentrytitle went into
the man page), and every "make" tried to rebuild it.

Release coming,
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman