From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: Jan Engelhardt <jengelh@inai.de>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
linux-modules <linux-modules@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-hotplug <linux-hotplug@vger.kernel.org>
Subject: Re: [ANNOUNCE] kmod 10
Date: Mon, 08 Oct 2012 13:41:37 +0000 [thread overview]
Message-ID: <CAKi4VAKt_TxM1mZ5aczL=e4jd1EGmr4bgTWfrX5nN+-z3YiWCA@mail.gmail.com> (raw)
In-Reply-To: <505695E3.7040603@gmail.com>
On Mon, Sep 17, 2012 at 12:15 AM, Bruce Dubbs <bruce.dubbs@gmail.com> wrote:
> Jan Engelhardt wrote:
>>
>>
>> On Thursday 2012-09-06 21:37, Lucas De Marchi wrote:
>>>
>>>
>>> kmod 10 is out:
>>>
>>> ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.xz
>>> ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-10.tar.sign
>>
>>
>> make check fails here with glibc-2.15, gcc-4.7, x86_64,
>> due to what seems to be duplicated symbols(?)
>
>
> On my LFS system, glibc-2.16, gcc-4.7.1, x86_64, I do not see these errors:
>
> ./configure --prefix=/usr --bindir=/bin --libdir=/lib \
> --sysconfdir=/etc --with-xz --with-zlib
> make
> make check
>
> =========
> All 9 tests passed
> =========
>
> What is interesting is that if I run the checks again:
>
> make check
>
> I get:
>
> TESTSUITE: running modprobe_softdep_loop, in forked context
> TESTSUITE: ERR: rootfs
> /usr/src/kmod/kmod-10/testsuite/rootfs/test-modprobe/softdep-loop is dirty,
> please run 'make rootfs' before runnning this test
> TESTSUITE: ERR: 'modprobe_softdep_loop' [16407] exited with return code 1
> TESTSUITE: ERR: FAILED: modprobe_softdep_loop
> FAIL: testsuite/test-modprobe
>
> TESTSUITE: running test_insert, in forked context
> TESTSUITE: ERR: rootfs /usr/src/kmod/kmod-10/testsuite/rootfs/test-init/ is
> dirty, please run 'make rootfs' before runnning this test
> TESTSUITE: ERR: 'test_insert' [16373] exited with return code 1
> TESTSUITE: ERR: FAILED: test_insert
> FAIL: testsuite/test-init
>
> =======================
> 2 of 9 tests failed
> Please report to linux-modules@vger.kernel.org
> =======================
>
> 'make rootfs' does not do anything but make distclean && configure && make
> && make check is clean for me.
"make rootfs" was completely wrong, it's fixed now and queued for kmod 11:
http://git.kernel.org/?p=utils/kernel/kmod/kmod.git;a=commit;h„afccb91db106ad81effc88c2851ceddeda06ea
and
http://git.kernel.org/?p=utils/kernel/kmod/kmod.git;a=commit;hÏ814054dd9a1f5240bc684769275e40ab81ba6e
Lucas De Marchi
next prev parent reply other threads:[~2012-10-08 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 19:37 [ANNOUNCE] kmod 10 Lucas De Marchi
2012-09-17 2:34 ` Jan Engelhardt
2012-09-17 3:15 ` Bruce Dubbs
2012-10-08 13:41 ` Lucas De Marchi [this message]
2012-10-08 13:38 ` Lucas De Marchi
2012-09-17 3:32 ` Dave Reisner
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='CAKi4VAKt_TxM1mZ5aczL=e4jd1EGmr4bgTWfrX5nN+-z3YiWCA@mail.gmail.com' \
--to=lucas.de.marchi@gmail.com \
--cc=bruce.dubbs@gmail.com \
--cc=jengelh@inai.de \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.demarchi@profusion.mobi \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).