LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [PATCH] Small In-Kernel Build Problem

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [PATCH] Small In-Kernel Build Problem
From: Horms <horms@xxxxxxxxxxxx>
Date: Thu, 21 Nov 2002 23:47:51 +0900
On Sun, Nov 10, 2002 at 12:24:24PM +0800, Wensong Zhang wrote:
> 
> 
> Hi Horms,
> 
> On Thu, 7 Nov 2002, Horms wrote:
> 
> > 
> > while trying to build lvs 1.0.6 in the kernel tree as non-modules
> > (don't ask why) I encounted some minor problems with symbol names.
> > The attached patch should resolve this.
> > 
> 
> I just tested compiling all the ipvs 1.0.6 in the kernel again, there was 
> no problem, gcc is of version 2.96.
> 
> The changes don't make a lot sense to me. 
> 
> -void ip_vs_app_cleanup(void)
> +void __exit ip_vs_app_cleanup(void)
> 
> The ip_vs_app_cleanup() will be called by the routines in ip_vs_core.c. 
> There should be no need to add __exit.
> 
> 
> -export-objs := ip_vs_core.o ip_vs_app.o
> +export-objs := ip_vs_core.o ip_vs_app.o ip_vs_conn.o ip_vs_sync.o
>  
> Only ip_vs_core.c and ip_vs_app.c have used the macro EXPORT_SYMBOL in the 
> code. And, ip_vs_sync.c doesn't export any symbol at all.
> 
> Please test it again or on the other box, let's find what the problem
> really is.

I was building this kernel using the debian build system.  Perhaps that
introduced some weirdness. I haven't been able to reproduce the problem
in a kernel.org tree. And the debian build system really wants you to
build modules anyway.  So it reall is a bit of a non-issue after all.

-- 
Horms
        


<Prev in Thread] Current Thread [Next in Thread>