[ydl-gen] Installing additional kernel modules on YDL5

[Bill Mueller]

Atro,

I can dig what you're saying, I've just went through this last
week using the kernel-headers package.  It sucks, but rather
than waste time figuring it out I just re-built the headers
correctly:

    - copy /lib/modules/<kernel version> /lib/modules/<kernel version>.orig
    - copy /usr/src/<kernel version>/kernel-x.y.x.ppc.config to .config
    - edit the Makefile, remove the "custom" tag from the VER=
    - make oldconfig
    - make
    - make modules_install
    - depmod -a

That fixed the symlinks and the System map issues I had.  Let me
know if that doesn't solve your linux/config.h issue too.  

Thanks for pointing out the symlink error.  I'll pass this
on to those that can address that directly, sorry for the 
hassle.

-Bill

On Sun, 7 Oct 2007 19:06:30 +0300 (EEST), Atro Tossavainen <atossava+ydl at cc.helsinki.fi> wrote:
> Bill,
> 
>> Probably not it, but take a look in /lib/modules/<kernel version>.
>> (<kernel version> should be whatever you get with a 'uname -r')
>>
>> You'll have two sym links in there called 'source' and 'build'.  May
>> want to check they point to the correct locations.
> 
> # ls -la /lib/modules/2.6.22-0.ydl.rc4/source
> lrwxrwxrwx 1 root root 57 Sep 17 12:56
> /lib/modules/2.6.22-0.ydl.rc4/source ->
> /home/owen/ydl5/kernel/BUILD/kernel-2.6.22/linux-2.6.22.0
> 
> I get the feeling I didn't create that symlink.  It's guaranteed to
> be wrong on any systems not internal to Yellow Dog, I suppose.
> 
> "build" is not a symlink, but a real directory.  Passing
> --with-linux-kernel-headers=/lib/modules/2.6.22-0.ydl.rc4/build
> to the OpenAFS configure process allows configure to finish, just
> as if I installed the kernel-source module, built a custom kernel,
> and passed that directory to confiugre, but the OpenAFS kernel module
> still can't be built - it bombs because linux/config.h does not exist:
> 
> env EXTRA_CFLAGS="" make -C /lib/modules/2.6.22-0.ydl.rc4/build
> M=/usr/src/openafs-1.4.2/src/libafs/MODLOAD-2.6.22-0.ydl.rc4-SP modules
> make[5]: Entering directory `/lib/modules/2.6.22-0.ydl.rc4/build'
> 
>   WARNING: Symbol version dump
> /lib/modules/2.6.22-0.ydl.rc4/build/Module.symvers
>            is missing; modules will have no dependencies and modversions.
> 
>   CC [M] 
> /usr/src/openafs-1.4.2/src/libafs/MODLOAD-2.6.22-0.ydl.rc4-SP/afs_atomlist.o
> In file included from
> /usr/src/openafs-1.4.2/src/libafs/MODLOAD-2.6.22-0.ydl.rc4-SP/afs_atomlist.c:11:
> /usr/src/openafs-1.4.2/include/afs/param.h:34:26: error: linux/config.h:
> No such file or directory
> make[6]: ***
> [/usr/src/openafs-1.4.2/src/libafs/MODLOAD-2.6.22-0.ydl.rc4-SP/afs_atomlist.o]
> Error 1
> make[5]: ***
> [_module_/usr/src/openafs-1.4.2/src/libafs/MODLOAD-2.6.22-0.ydl.rc4-SP]
> Error 2
> make[5]: Leaving directory `/lib/modules/2.6.22-0.ydl.rc4/build'
> make[4]: *** [libafs.ko] Error 2
> make[4]: Leaving directory
> `/usr/src/openafs-1.4.2/src/libafs/MODLOAD-2.6.22-0.ydl.rc4-SP'
> make[3]: *** [linux_compdirs] Error 2
> make[3]: Leaving directory `/usr/src/openafs-1.4.2/src/libafs'
> make[2]: *** [libafs] Error 2
> make[2]: Leaving directory `/usr/src/openafs-1.4.2'
> make[1]: *** [build] Error 2
> make[1]: Leaving directory `/usr/src/openafs-1.4.2'
> make: *** [all] Error 2
> 
> Why does it have to be unintuitive like this?  You'd expect the repo
> to have a "kernel-devel" package that installed a working set of
> kernel headers in the expected place under /usr/src/kernels.  Well,
> *I* would expect that.
> 
> --
> Atro Tossavainen (Mr.)               / The Institute of Biotechnology at
> Systems Analyst, Techno-Amish &     / the University of Helsinki, Finland,
> +358-9-19158939  UNIX Dinosaur     / employs me, but my opinions are my
> own.
> < URL : http : / / www . helsinki . fi / %7E atossava / > NO FILE
> ATTACHMENTS
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'