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

[Stuart Hughes]

Can you try removing (or moving) the source tree for zaptel and then
just run ./ltib -p zaptel so it does all the stages (and removed the
source).  When I do this it works fine.

S.

On Tue, 2008-10-21 at 17:08 +0200, Vadim Lebedev wrote:
> Ok,
> 
> I'm attaching logs of all  stages
> 
> What is interesting:
> The generated rpm file contains ONLY device nodes  and they ARE
> deployed
> The binaries and kernel modules howevere are not
> 
> 
> Thanks
> Vadim
> PS  If you try to build zaptel yourself you need to active in kernel
> config
> in library functions/crc_ccitt 
> 
> 
> 
> 
> 
> Stuart Hughes wrote: 
> > Hi Vadim,
> > 
> > If you run ./ltib to build zaptel, it will install the result if it
> > builds. If not, please send the output.
> > 
> > If you're in single package mode, you need to run:
> > 
> > ./ltib -p <pkg> -m scbuild         : to build
> > ./ltib -p <pkg> -m scdeploy        : to install/deploy on rootfs
> > 
> > -m scinstall only installs into the tmp/pkg area, this is a packaging
> > test (for rpm).
> > 
> > If this isn't working properly, please send some output.
> > 
> > Regards, Stuart
> > 
> > On Tue, 2008-10-21 at 16:15 +0200, Vadim Lebedev wrote:
> >   
> > > Stuart,
> > > 
> > > I do intend to modify zaptel sources
> > > 
> > > but i've tried ./ltib 
> > > too..
> > > 
> > > With the same result
> > > 
> > > Stuart Hughes wrote: 
> > >     
> > > > Hi Vadim,
> > > > 
> > > > You should not be running like that unless you're developing a single
> > > > package.
> > > > 
> > > > You should instead select the package and simply run: ./ltib
> > > > 
> > > > Regards, Stuart
> > > > 
> > > > On Tue, 2008-10-21 at 14:57 +0200, Vadim Lebedev wrote:
> > > >   
> > > >       
> > > > > Estevam Fabio wrote: 
> > > > >     
> > > > >         
> > > > > > Vadim,
> > > > > >  
> > > > > > Did you run ./ltib -p <packagename> -m scdeploy ?
> > > > > >  
> > > > > > Regards,
> > > > > >  
> > > > > > Fabio Estevam
> > > > > > 
> > > > > >       
> > > > > >           
> > > > > I did:
> > > > > 
> > > > > ./ltib -m scdeploy  -p zaptel
> > > > > 
> > > > > 
> > > > > I suppose it is equivalent
> > > > > 
> > > > > Thanks
> > > > > Vadim
> > > > >     
> > > > >         
> > > > > > ____________________________________________________________________
> > > > > > From: address@hidden
> > > > > > [mailto:address@hidden On
> > > > > > Behalf Of Vadim Lebedev
> > > > > > Sent: Tuesday, October 21, 2008 10:41 AM
> > > > > > Cc: ltibext
> > > > > > Subject: Re: [Ltib] Out of tree kernel and in-tree modules
> > > > > > 
> > > > > > 
> > > > > > 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
> > > > >     
> > > > >         
> > > >   
> > > >       
> > 
> > 
> >   
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib