Thanks for your prompt respone. The architecture I am working on is amd64 aka x86_64, opteron/xeon servers with
redhat enterprise 4 update 5 and update 6.

For the pvfs-2.7.0 indeed the make distclean helps with the initial problem, so something must be included in the archive that was not supposed to be there. I uploaded my copy as I downloaded it on http://www.quickfilepost.com/download.do?get=a8811c0c7a4d56eb16dd7d655d4cb858 and my build-tree after prepare ; ./configure --with-kernel=/usr/src/kernels/linux-2.6/ --disable-kernel-aio ; make kmod is on http://www.quickfilepost.com/download.do?get=4e30a6ec25ee4997f3bbd044605eb28d

76cb0e1b921b908f16cb24de451e7ce4  pvfs-2.7.0.rhel4u5.tar.gz
99e7680e82b692f699b5a295b31989c8  pvfs-2.7.0.tar.gz

However the kmod still complains about *** Warning: "class_device_destroy" [/root/pvfs-2.7.0/src/kernel/linux-2.6/pvfs2.ko] undefined! and pvfs2-config.h has #define HAVE_KERNEL_DEVICE_CLASSES 1 defined, which prevents loading the module, regardless
of --disable-kernel-aio.

I will next try to give pvfs-2.6.3 a spin...

Michael


Robert Latham wrote:
On Mon, Jan 28, 2008 at 01:01:33PM -0800, Michael Will wrote:
Since pvfs2.7.0.tar.gz as downloadable from ftp://ftp.parl.clemson.edu/pub/pvfs2/pvfs-2.7.0.tar.gz does not compile on redhat enterprise 4 systems, make: *** No rule to make target `/usr/include/bits/syslog-path.h', needed by `src/server/unexpected.d'. Stop.

Hm. Odd. I've built on RHEL 4, so I'm pretty sure that *should* work.
We have for some reason gotten a lot of these sorts of bug reports.
Every time a "make distclean" followed by a configure/make/make kmod
makes the problem go away.

Do you still happen to have your pvfs-2.7.0 tree?  Could you tar it up
and post it on a web or ftp site somewhere? If not, no big deal.
I checked out the more recent 2.7.1pre sourcetree from CVS.

It does seem to compile just fine, however when I attempt to compile the kernel-module, it complains because of the missing function src/kernel/linux-2.6/devpvfs2-req.c: class_device_destroy(pvfs2_dev_class, MKDEV(pvfs2_dev_major, 0)) and
in consequence the module created does not load.


What architecture is this?  On ia64 I had to build with --disable-kernel-aio

Which version of PVFS is best suited for running on RHEL4 - and what level of confidence do the developers have with the outcome?

We go through a lot of effort to keep backwards compatiblitiy with
old kernels while supporting the latest 2.6 kernel API changes.  It's
possible we missed something.  It's also likely that the redhat 2.6.9
kernel has been patched to such an extent that we might need an
additional configure check or two.

Did pvfs-2.6.3 work out ok?

What "additional patches" did the failing kernel have?

==rob

_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to