Opened 18 years ago

Closed 18 years ago

#1858 closed defect (worksforme)

Missing "make" in Module-init-tools testsuite ?

Reported by: Seb Owned by: lfs-book@…
Priority: normal Milestone:
Component: Book Version: 6.1.1
Severity: trivial Keywords: module-init-tools
Cc:

Description

Hello,

I don't know if it's revelant, but I experienced a problem with the module-init-tools testsuite (LFS 6.1.1).

When I entered all the commands as they were given in the book (just modified according to the errata), I obtained this result :

tar -xvf /sources/module-init-tools-testsuite-3.1.tar.bz2
--strip-components=1 && 
./configure && 
make check

[...]

make  check-TESTS
make[1]: Entering directory `/dev/shm/module-init-tools-3.1'
Building with --enable-zlib...
insmod.o(.text+0x5bf): In function `modtest_gzopen':
/tmp/module-init-tools-3.1/testing.h:196: undefined reference to
`gzopen' collect2: ld returned 1 exit status
make[2]: *** [insmod.static] Error 1
FAIL: tests/runtests
===================
1 of 1 tests failed
===================
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory `/dev/shm/module-init-tools-3.1'
make: *** [check-am] Error 2

I think a make is missing here, because when I had it, the test was successful :

tar -xvf /sources/module-init-tools-testsuite-3.1.tar.bz2
--strip-components=1 && 
./configure &&
'''make &&'''
make check

[...]

make  check-TESTS
make[1]: Entering directory `/dev/shm/module-init-tools-3.1'
Building with --enable-zlib...
Testing with --enable-zlib...
Running tests for tests/test-depmod...............
Running tests for tests/test-generate-modprobe.conf......
Running tests for tests/test-insmod.....
Running tests for tests/test-lsmod.....
Running tests for tests/test-modinfo.....
Running tests for tests/test-modprobe...........................
Running tests for tests/test-rmmod.......
Building with --disable-zlib...
Testing with --disable-zlib...
Running tests for tests/test-depmod...............
Running tests for tests/test-generate-modprobe.conf......
Running tests for tests/test-insmod.....
Running tests for tests/test-lsmod.....
Running tests for tests/test-modinfo.....
Running tests for tests/test-modprobe...........................
Running tests for tests/test-rmmod.......
PASS: tests/runtests
==================
All 1 tests passed
==================
make[1]: Leaving directory `/dev/shm/module-init-tools-3.1'

I hope it will be useful for you.

Take care, Seb.

Change History (7)

comment:1 by Seb, 18 years ago

Type: taskdefect

comment:2 by bdubbs@…, 18 years ago

Resolution: wontfix
Status: newclosed

I'm not sure if this is valid or not, but since LFS 6.2 is released, this is, at a minimum, overcome by events.

comment:3 by Matthew Burgess, 18 years ago

I don't think it is valid, to be honest. I've certainly never seen that error before, nor has it ever been reported. As frustrating as it no doubt is, my only suggestion is for the reporter to try the latest version of the book (6.2).

comment:4 by dnicholson@…, 18 years ago

At the very least, substituting module-init-tools-3.2.2 from the current stable book would be necessary. I don't think anyone's built 3.1 around here in a while.

comment:5 by Seb, 18 years ago

Hello,

I tryed to build module-init-tools-3.2.2, and it worked. In order to be sure the "problem" was fixed with this version of module-init-tools, I remade the test with module-init-tools-3.1 and... it worked too.

I don't understand why, but now the the LFS system is complete, there is no more problem (and I tested the issue many times before posting it, so I'm sure it really didn't work in Chapter 6).

However, it means this "problem" isn't persistent, so I think it isn't worth fixing it too.

Best regards, Seb.

comment:6 by Matthew Burgess, 18 years ago

Resolution: wontfix
Status: closedreopened

comment:7 by Matthew Burgess, 18 years ago

Resolution: worksforme
Status: reopenedclosed

Thanks for confirming that the current instructions work, Seb.

Note: See TracTickets for help on using tickets.