--On Saturday, October 23, 2004 13:18:08 -0400 John F Davis <[EMAIL PROTECTED]> wrote:
> Originally I tried openafs 1.2.3 with 2.4.17. It had the same > sys_call_table32 error when I built it with 2.4.27. After that is when I > tried to using the newer version of openafs. 2.4.27 (and 2.4.17 and 2.4.18 and 2.4.24) properly export sys_call_table32. I do not know why you are having this problem. > About your successfull build, are you using egcs or gcc? And, could you > post your .config? I'm using sarge's gcc. I did not build my own 2.4.27 kernel, so I do not have a .config for that I'm using the 2.4.24 module I built with the stock debian 2.4.24-sparc64 kernel, and built the module against a tree configured with the default sparc64 .config (configs/sparc64 from the kernel-image-sparc source package) > I just built a module in this way, and it looks like it's not going > to load > > It has some references that I don't think will resolve: > U > U > U > U current It appears that these are artifacts of the way sparc64 kernel modules are built. My working 2.4.24 module has the same references, and does load and work (on 2.4.24). Some of the modules included in the kernel-image-2.4.24-sparc64 package also have them. I can't arbitrarily reboot this machine to test it
p7sE17uTsWu0N.p7s
Description: S/MIME cryptographic signature
