Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)

On Thu, Sep 07, Kirill Korotaev wrote:

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

It clearly depends on the context. An unimportant dvb module may have
unresolved symbols, but the drivers for your root filesystem should
rather not have unresolved symbols.

Better leave the current default, your patch seems to turn an unresolved
symbol with "unknown importance" into a hard error.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
  - From: Adrian Bunk <[email protected]>

References:
- [PATCH] fail kernel compilation in case of unresolved symbols (v2)
  - From: Kirill Korotaev <[email protected]>

Prev by Date: Re: [PATCH] Fix longstanding load balancing bug in the scheduler.
Next by Date: Re: [patch 29/37] dvb-core: Proper handling ULE SNDU length of 0
Previous by thread: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
Next by thread: Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]