Re: [Ltib] Out of tree kernel and in-tree modules

[Stuart Hughes]

Hi Vadim,

Did you get it to build?  I saw your other message on the zaptel list:

  CC [M]  /home/vadim/ltib/rpm/BUILD/zaptel-1.4.11/kernel/zttranscode.o
  Building modules, stage 2.
  MODPOST 4 modules
WARNING: "crc_ccitt_table" 
[/home/vadim/ltib/rpm/BUILD/zaptel-1.4.11/kernel/zaptel.ko] undefined!
...

If you did you should have seen it get installed:

+ exit 0
Build time for zaptel: 37 seconds

sudo /opt/ltib/usr/bin/rpm --root /home/seh/ltib_bsps/savannah_ltib/rootfs 
--dbpath /var/lib/rpm -e --allmatches --nodeps --define '_tmppath /tmp/ltib' 
zaptel 2>/dev/null
sudo /opt/ltib/usr/bin/rpm --root /home/seh/ltib_bsps/savannah_ltib/rootfs 
--dbpath /var/lib/rpm --prefix / --ignorearch -ivh --force --excludedocs 
--define '_tmppath /tmp/ltib' 
/home/seh/ltib_bsps/savannah_ltib/rpm/RPMS/arm/zaptel-1.4.11-1.arm.rpm
Preparing...                ########################################### [100%]
   1:zaptel                 ########################################### [100%]

Started: Tue Oct 21 13:57:13 2008
Ended:   Tue Oct 21 13:57:59 2008
Elapsed: 46 seconds

You can check where it went with the following (note my build was for
imx31 as I had that setup, remember this is relative to rootfs):

$ rpm --root `pwd`/rootfs -ql zaptel
//dev/zap/1
//dev/zap/10
//dev/zap/100
//dev/zap/101
....
//sbin/fxotune
//sbin/ztcfg
//sbin/ztmonitor
//sbin/ztscan
//sbin/ztspeed
//sbin/zttest
//usr
//usr/include
//usr/include/zaptel
//usr/include/zaptel/tonezone.h
//usr/include/zaptel/zaptel.h
//usr/lib
//usr/lib/libtonezone.a
//usr/lib/libtonezone.so
//usr/lib/libtonezone.so.1
//usr/lib/libtonezone.so.1.0
//usr/share
//usr/share/man
//usr/share/man/man8
//usr/share/man/man8/fxotune.8
...

If you don't get that, what command line did you use for ltib?

Regards, Stuart

On Tue, 2008-10-21 at 14:41 +0200, Vadim Lebedev wrote:
> Stuart 
> 
> Thanks a lot for the advice,
> 
> I'm now able to compile zaptel,
> There is still a problmem with deploying
> Somehow the zaptel build results are not installed into the rootfs
> but in tmp/zaptel/opt/freescale/rootfs/arm
> 
> Any ideas?
> Thanks
> Vadim
> 
> 
> 
> Stuart Hughes wrote: 
> > Hi Vadim,
> > 
> > On Mon, 2008-10-20 at 16:15 +0200, Vadim Lebedev wrote:
> >   
> > > Hello
> > > 
> > > I'm working with savannah ltib
> > > 
> > > I've somewhat unusual config:
> > > I've have a kernel built out of LTIB tree 
> > > but i have an in-tree kernel module (zaptel) which need to reference
> > > the kernel's .config and .h files.
> > > How can i arrange for this?
> > > 
> > >     
> > 
> > If you run $./ltib -m config you can select: "Include kernel headers" it
> > will install the kernel headers in rootfs/usr/src/linux/ and in your
> > spec file you can refer to these as (for example with see
> > dist/lfs-5.1/iproute/iproute.spec):
> > KERNEL_INCLUDE=$DEV_IMAGE/usr/src/linux 
> > 
> > Note also that config file gets put into rootfs/linux.config
> > ($DEV_IMAGE/boot/linux.config).
> > 
> > If this is not enough and you need the whole built kernel tree left
> > unpacked, you can select (in ./ltib -m config):
> > "Leave the sources after building"
> > 
> > This will leave the built kernel sources unpacked in rpm/BUILD/linux and
> > you can refer to these from other spec files as: $RPM_BUILD_DIR/linux
> > See: dist/lfs-5.1/helloworld/hello_mod.spec for an example.
> > 
> >   
> > > Antohere problem:
> > > This time in-tree kernel for imx27ads
> > > and still trying to build zaptel kernel module
> > > the kerenel build's ok but when zaptel is compiled
> > > it does not find   blablabla/linux/.config
> > > 
> > > 
> > > I know it worked 2 monthes ago, but i'm unable to find what i'm
> > > doing wrong this time.
> > >     
> > 
> >   
> > > I see that the kernel is built it's rpm is created and installed but
> > > in the rpm/BUILD dirctory there is no linux directory  so zaptel build 
> > > is screwed...
> > > 
> > >     
> > 
> > It's probably a change in configuration?  I don't understand though how
> > this can happen as if you look in config/userspace/packages.lkc you
> > should see:
> > 
> > config PKG_ZAPTEL
> >     bool "zaptel"
> >     select PKG_KERNEL_LEAVESRC
> > 
> > This should be enough to force the sources to remain unpacked.  Can you
> > run ./ltib -m config and scroll down to the kernel area and check that 
> > "Leave the sources after building" is enabled.
> > 
> > Regards, Stuart
> > 
> > 
> > 
> > 
> >   
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib