OpenVZ Forum


Home » Mailing lists » Devel » [PATCH] fail kernel compilation in case of unresolved symbols (v2)
Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2) [message #6065 is a reply to message #6060] Thu, 07 September 2006 15:20 Go to previous messageGo to previous message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member

Olaf Hering wrote:
> On Thu, Sep 07, Adrian Bunk wrote:
>
>
>>If any module shipped with the kernel has in any configuration
>>unresolved symbols that's a bug that should be reported, not ignored.
>
>
> Yes, but on request when building the package. Not per default.
> I probably missed the reason why this is now suddenly a problem.
It is not that sudden at all. I experienced this problem many times so far
and working with a build system came to the idea of failing
builds when there are unresolved symbols.

I'm pretty sure that having this patch in mainstream
will make unresolved symbols a rare problem as many of them will be fixed soon.
So I'm pretty agree with Adrian that modules with unresolved symbols is a bug
and it MUST be fixed.
I would be very much interested to hear Andrew opinion on this as
he probably makes kernels even more often than any of us :)

Thanks,
Kirill
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: [stable] [PATCH] IA64, sparc: local DoS with corrupted ELFs
Next Topic: Re: Re: [RFC][PATCH] Rename pspace to pid_namespace
Goto Forum:
  


Current Time: Fri Aug 22 02:05:08 GMT 2025

Total time taken to generate the page: 0.10770 seconds