Re: [PATCH 18/28] kbuild: fail kernel compilation in case of unresolved module symbols

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 25, 2006 at 12:47:40AM +0200, Sam Ravnborg wrote:
> > That's out of 25 targets.  The only variants that do _NOT_ trigger are
> > amd64, amd64-UP, i386 and uml-amd64.
> 
> How many of these ougth to be fixed then?

In theory - all of them.  Right now that's just plain not feasible...

> > I more or less agree with rationale behind making that default, but I'd
> > very much appreciate a way to override that.  For now I've just made the
> > -w line unconditional, but the fewer infrastructure patches I've to carry...
> OK. Will include it in next round of kbuild updates.

BTW, an alternative would be to stop unconditionally after full set of checks
and not bother with .mod.o/.ko at all.  _Not_ as a default, of course...
-
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/

[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]
  Powered by Linux