Modify

Opened 8 years ago

Closed 7 years ago

#45 closed enhancement (fixed)

fail to compile module-init-tools with docbook2man

Reported by: dmontaldo@dc.uba.ar Owned by: bas
Priority: critical Milestone: SALI 1.6.0
Component: sali Version: trunk
Keywords: debian, debian wheezy Cc:

Description

I try to compile module tools in a debian wheezy from the sara repository.

It fails with this errors.

if [ "docbook2man" = "docbook2man" ]; then                     \
            docbook2man ../doc/modprobe.d.sgml > /dev/null 2>&1;                       \
        else                                                               \
            docbook2man ../doc/modprobe.d.sgml 2>&1 > modprobe.d.5 | sed 's/^[^:]*://';              \
        fi
make[2]: *** [modprobe.d.5] Error 127
make[2]: *** Waiting for unfinished jobs....

It's look like a docbook2man error from the docbook-utils package because I try with the official version 3.12 3.13 3.14 and 3.15 and all fails in the same step.

I'm really stuck in this step so I start reading log files and after reading in details the configure step I found this:

checking for docbook-to-man... no
checking for docbook2man... docbook2man

So I try to install docbook-to-man and now it compiles with all the official version and even with the sali version too.

Maybe you should take a look at this and only use docbook-to-man because with docbook2man fails. Or maybe document more the make build step...

If you want to document more the build step I have a list of dependencies, at least for debian, to compile sali.

I hope this could help someone else.
Thanks,
Damián.

Attachments (0)

Change History (6)

comment:1 follow-up: Changed 8 years ago by bas

  • Owner changed from somebody to bas
  • Status changed from new to accepted
  • Type changed from defect to enhancement

Thanks, can you add the list of dependencies? So we can update the script and the wiki

comment:2 in reply to: ↑ 1 Changed 8 years ago by dmontaldo@dc.uba.ar

Replying to bas:

Thanks, can you add the list of dependencies? So we can update the script and the wiki

The list of dependencies to compile sali in debian? Which script you want to update?

At least I got this list in wheezy but I don't use sali right now because it can't boot with out the boot flag on (see #41) and I can't finish the make step yet to have the complete list.

openssl libssl-dev libxml2 libxml2-dev libusb-dev libusb-1.0-0-dev gperf libglib2.0-dev libacl1 libacl1-dev linux-libc-dev libv4l-dev docbook-utils

If you want I have all the dependency errors to every package in the list.

Anyway I think that the desirable situation is that the configure step fails after start compiling.
Or even a better idea: if you pretend to make a list of debian dependencies then buil a debian package that depend on that list ;)

Thanks.

comment:3 Changed 8 years ago by bas

Damián,

we usually build in a clean VM or node and use this script to install the proper packages

Most people are only interested in the kernel/initrd and server tools and as already told the building of these tools is rather complex and depends on a lot of packages. We compile it on SUSE (Power6) and Debian (X86_64). We use the compiled kernel/initrd to install different Linux Flavours. So SALI is not debian specific ;-)

You can also set the boot flag in your master script to bypass the bug you reported (#41). You have complete control howto install a node. You can use the sali functions that hide some complexity or you can use the bare bone commands as setting the boot flag on a partition.

comment:4 Changed 8 years ago by bas

(In [512]) added more dependencies, Thanks to Damian, see #45

comment:5 Changed 8 years ago by dennis

  • Milestone set to SALI 1.6.0

comment:6 Changed 7 years ago by dennis

  • Resolution set to fixed
  • Status changed from accepted to closed

module-init-tools has been replaced by kmod, so this ticket is obsolete

Add Comment

Modify Ticket

Change Properties
Action
as closed The owner will remain bas.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.