Hi Peng,
Yep, It looks like you would have to use CVS for the time being instead of
the 1.4 release on FC5
since we did not have configure checks for update_atime() etc in the
release.
Thanks,
Murali


On Mon, 15 May 2006, Peng Gu wrote:

> My systems are installed with FC5 official release. On my systems, "#
> uname -r " says 2.6.15-1.2054_FC5smp. With this in mind, I installed
> the corresponding kernel source using "rpm -ivh
> kernel-smp-devel-2.6.15-1.2054_FC5.i686.rpm".
>
> And then I created a link to it:
> # ln -s /usr/src/kernels/2.6.15-1.2054_FC5-smp-i686  
> /usr/src/kernels/linux-2.6
>
> At this point, I ran the pvfs2 configure tool
> #./configure --with-kernel=/usr/src/kernels/linux-2.6
>
> After all these steps,  insmod still complains:
>
> #insmod src/kernel/linux-2.6/pvfs2.ko
> insmod: error inserting
> '/usr/src/pvfs2/src/kernel/linux-2.6/pvfs2.ko': -1 Unknown symbol in
> module
>
> And here is the related message from "# dmesg":
> pvfs2: Unknown symbol update_atime
>
> The good news is that: the insmod problem disappears when I build the cvs 
> tree.
> The PVFS2 version string was 1.4.1pre1-2006-05-15-212716.
>
> Thanks,
> Peng
>
>
> On 5/15/06, Murali Vilayannur <[EMAIL PROTECTED]> wrote:
> > Hi Peng,
> > Can you point configure to the running kernel's headers/source/build
> > directory and see if things work? You could see this error because of an
> > incorrect path to --with-kernel..
> > Murali
> >
> > On Mon, 15 May 2006, Peng Gu wrote:
> >
> > > Follow up: dmesg complains the same thing when building directly from
> > > the CVS tree.
> > >
> > >
> >
>
>
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to