Tom,
DId you rerun configure on PVFS2 with
--with-kernel=/path/to/newest/kernel sources?
It is best if you make clean prior to rerunning configure?
Sorry that it is taking you longer than it takes normally..
Please let us know how/what is going wrong and I am sure we can figure this out
and get you going soon.
It is a case of wrong build tool version/kernel sources.
thanks,
Murali
On 5/30/07, Tommy Butler <[EMAIL PROTECTED]> wrote:
I installed the latest kernel package from Debian (compiled with gcc 4.1),
the corresponding source. I prepared the kernel source build tree as I
would normally do.
I got to the same point and experienced the same failure again, this time
with a slightly different error message from dmesg. I must admit, I'm
almost ready to abandon this venture. It's proving to be more of a hassle
than I can justify for hours billed. It's not looking good.
Maybe some insight on this anyone, before I scrap it all?
during `make kmod_install`:
[EMAIL PROTECTED]:/usr/src/pvfs2# make kmod_install
WARNING: Symbol version dump /usr/src/linux-source-2.6.18/Module.symvers
is missing; modules will have no dependencies and modversions.
after `insmod pvfs2.ko`:
[EMAIL PROTECTED]:/usr/src/pvfs2/src/kernel/linux-2.6# uname -a
Linux node2 2.6.18-4-486 #1 Wed May 9 22:23:40 UTC 2007 i686 GNU/Linux
[EMAIL PROTECTED]:/usr/src/pvfs2/src/kernel/linux-2.6# insmod
pvfs2.ko
insmod: error inserting 'pvfs2.ko': -1 Invalid module format
[EMAIL PROTECTED]:/usr/src/pvfs2/src/kernel/linux-2.6# dmesg|tail
-n1
pvfs2: version magic ' 2.6.18 mod_unload 486 gcc-4.1' should be
'2.6.18-4-486 mod_unload 486 REGPARM gcc-4.1'
...I'll keep plugging away at it. Again, I thank in advance all who provide
your assistance.
Many thanks,
--
Tommy Butler
On 5/30/07, Robert Latham <[EMAIL PROTECTED]> wrote:
> On Wed, May 30, 2007 at 09:34:45PM -0500, Tommy Butler wrote:
> > [EMAIL PROTECTED] dangit. Well I do so very much appreciate your rapid
response.
I'll
> > work on sorting out the differences between gcc and my kernel. PVFS is
a
> > must have for this cluster.
>
> Hi Tommy
>
> Here's one thing we've done on our debian testing machines when the
> compiler got upgraded before the kernel. It's kind of gross, but
> works.
>
> Go ahead and install the older gcc-4.0 package. The gcc symlink
> /usr/bin/gcc will still point to the "default" gcc version, and is the
> gcc the kernel build system will try to use. You may have some
> specific reasons why you can't install gcc-4.0 but there's a pretty
> good chance you'll be able to install multiple gcc packages without
> problem.
>
> /usr/bin/gcc probably points to /usr/bin/gcc-4.1 on your box. Go
> ahead and temporarily make that link point to /usr/bin/gcc-4.0 while
> you make the pvfs2.ko module. Probably would be a good idea to reset
> the link after you've built pvfs2.ko
>
> The "debian way" to fix this might be to rebuild the debian kernel
> package. Not sure if the compiler is an explicit build-dep though.
>
> Either of those approaches work for you?
> ==rob
>
> --
> Rob Latham
> Mathematics and Computer Science Division A215 0178 EA2D B059 8CDF
> Argonne National Lab, IL USA B29D F333 664A 4280 315B
>
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
