[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060924222026.GS29920@ftp.linux.org.uk>
Date: Sun, 24 Sep 2006 23:20:26 +0100
From: Al Viro <viro@....linux.org.uk>
To: sam@...nborg.org
Cc: linux-kernel@...r.kernel.org, Kirill Korotaev <dev@...nvz.org>,
Andrey Mirkin <amirkin@...ru>, Andrew Morton <akpm@...l.org>
Subject: Re: [PATCH 18/28] kbuild: fail kernel compilation in case of unresolved module symbols
On Sun, Sep 24, 2006 at 11:18:14PM +0200, sam@...nborg.org wrote:
> From: Kirill Korotaev <dev@...nvz.org>
>
> At stage 2 modpost utility is used to check modules. In case of unresolved
> symbols modpost only prints warning.
>
> IMHO it is a good idea to fail compilation process in case of unresolved
> symbols (at least in modules coming with kernel), since usually such errors
> are left unnoticed, but kernel modules are broken.
>
> - new option '-w' is added to modpost:
> if option is specified, modpost only warns about unresolved symbols
>
> - modpost is called with '-w' for external modules in Makefile.modpost
Oh, joy... Could you add a way to tell kbuild that old behaviour is,
in fact, desired? make MODPOST_FLAGS=-w or something along these lines...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists