[OpenAFS-devel] problem configuring current cvs on 2.4.20-pre7...

[Neulinger, Nathan]

Looks like this is probably the problem:

                 if test "$ac_cv_linux_config_modversions" =3D "xno"; =
then
                   AC_MSG_WARN([Cannot determine sys_call_table status.
assuming it's exported])
                   ac_cv_linux_exports_sys_call_table=3Dyes
                 else
                   LINUX_EXPORTS_SYS_CALL_TABLE
                   LINUX_EXPORTS_KALLSYMS_SYMBOL
                   LINUX_EXPORTS_KALLSYMS_ADDRESS
                   LINUX_EXPORTS_INIT_MM
                   if test "x$ac_cv_linux_exports_sys_call_table" =3D
"xno"; then

It's missing the "x" in front of the
"x$ac_cv_linux_config_modversions"...=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216


> -----Original Message-----
> From: Neulinger, Nathan=20
> Sent: Wednesday, December 04, 2002 3:53 PM
> To: openafs-devel@openafs.org
> Subject: [OpenAFS-devel] problem configuring current cvs on=20
> 2.4.20-pre7...
>=20
>=20
> Was working fine a few weeks ago, but with new sys call table
> lack-of-export handling stuff, does not work any more:
>=20
> checking for i_dirty_data_buffers in struct inode... yes
> checking for i_devices in struct inode... yes
> checking for inode_setattr return type... yes
> checking for linux/completion.h existance... no
> checking for exported tasklist_lock... no
> checking for redhat kernel configuration... no
> checking if kernel uses MODVERSIONS... no
> checking which kernel modules to build... MP SP
> checking for exported sys_call_table... no
> checking for exported kallsyms_symbol_to_address... no
> checking for exported kallsyms_address_to_symbol... no
> checking for exported init_mm... no
> configure: error: no available sys_call_table access method
>=20
>=20
> This is a standard kernel, not a goofy redhat custom one.=20
> Note, I do NOT
> use module symbol versions. Are the sys_call_table and other checks
> breaking without MODVERSIONS? (They look to be checking for _ver_....
> symbols.)
>=20
> I'll dig into this a bit, but figured that whoever added this=20
> code might
> have an idea how to unbreak it.=20
>=20
> -- Nathan
>=20
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  nneul@umr.edu
> University of Missouri - Rolla         Phone: (573) 341-4841
> Computing Services                       Fax: (573) 341-4216
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20