RE: [Trinux-talk] Building a package

[Kris B. <Kri...@sc...>]

 Unresolved symbols are also a result of a modules for the same version of
the kernel being compiled against a kernel which was built with different
options. 'kmalloc_Rsmp' would imply that the module was compiled against a
SMP enabled kernel, but the target kernel wasn't compiled with SMP support
enabled. 
 
 To effectively build new modules against the trinux kernel we need a copy
of the the .config file that Mathew used when he built the kernel used in
5sep02.iso. There are .config's for some earlier kernels available at
http://trinux.sourceforge.net/kernel/2.4.5/
<http://trinux.sourceforge.net/kernel/2.4.5/>  , but not for the one that
.iso . We need to ask him _really_nicely_ to post it somewhere...
 
 It's worth noting that the latest kernels include the "CONFIG_IKCONFIG"
option, which effectively bundles the .config file into the kernel image,
but that isn't really an appropriate soloution for a space-restricted
distribution.
 
:-)

-----Original Message-----
From: Scott O. [mailto:sol...@ho...]
Sent: November 5, 2002 9:53 AM
To: tri...@li...
Subject: [Trinux-talk] Building a package


I am using the 5sep02.iso image of Trinux.  On a Slackware 7.1 machine, I
compiled a new kernel (2.4.19)
for it, so that it would match the version of the kernel that the 5sep02.iso
image of Trinux was using.  
I have a package that I wanted to build for Trinux, so I installed it on the
Slackware machine and 
then tared up the file into example.tgz.  This package did however need the
kernel sources to install, 
which I had the 2.4.19 kernel sources on there for.  I then inserted the tgz
file into the iso image, 
burned a cd, etc.  Now from Trinux, I try to start the script for my new
software package which happens 
to load a module that I have as part of the tgz file and it is there in
Trinux - but I get insmod errors.  
There are about 15-20 of them, an example follows =   insmod: unresolved
symbol kmalloc_Rsmp_93d4cf36.
 
Does anyone have any ideas?  I know these unresolved symbols are usually due
to different kernel versions 
from the one I am using.  But I have made sure that I am using 2.4.19 and
that the version of Trinux is 
in fact 2.4.19.  The one thing that I did notice about the Trinux version
was that it looks like it may 
have been built on Debian, should this matter?
 
Thanks for any help,
 
Scott