Re: [rock-user] rock-user Digest, Vol 18, Issue 5

Thanks for the answers.
> > I would like to create a static kernel.
>
> Are you trying to build a "kitchen sink" kernel, or a custom kernel
> for your particular hardware? I would strongly advise building a
> kernel containing just those selections that you need, especially if
> your are building it static.
>
> First, you need a working linux .config. If you want a static kernel,
> make sure that everything is "=y", and there are no "=m"s.
>
> To build a kernel with a custom .config, the best thing to do is to
> create a new target.
>
> 1) create a new directory in <rock root>/targets
>
> 2) create the following files in that directory
>
> build.sh
>         this can simply contain the line
>
> . target/generic/build.sh
>
> config.in
>         See <http://doc.rocklinux.org/wiki/CreatingTargets>
>
>         make sure there it contains the line
>
> export ROCKCFGSET_PKG_LINUX_CUSTCONFIG='1'
>
> linux.cfg
>         copy your linux .config here
>
> preconfig.in
>         this contains a comment line describing the target -
>         underscores in the comment are replaced with spaces when the
>         line is displayed.
>
> Then run
>
> ./scripts/Config -cfg <name>
>
> and select your target in the "Target Distribution" section.
>
> then
>
> ./scripts/Build-Pkg -cfg <name> linux26
>
>
> --
> Alan J. Wylie                                         
> http://www.wylie.me.uk/ "Perfection [in design] is achieved not when there
> is nothing left to add, but rather when there is nothing left to take
> away."
>   -- Antoine de Saint-Exupery
>
All done, it builds the kernel as static. However, the Build-Pkg "fails" to 
build modules as it discovers no module support.
>
> ------------------------------
>
> Alan J.Wylie wrote:
> > On Sun, 30 Oct 2005 10:37:16 +0100, Blacky <[email protected]> said:
> >>I would like to create a static kernel.
> >
> > To build a kernel with a custom .config, the best thing to do is to
> > create a new target.
>
> That's not quite correct. The easiest way is to just create the
> configuration with scripts/Config, select "Custom Linux Kernel
> Configuration" and then just dump the .config into
> config/<configname>/linux.cfg.
>
> HTH,
> 	Benjamin
> --
> Benjamin 'blindCoder' Schieder
> Registered Linux User #289529: http://counter.li.org
> finger blindcoder-1k+CIuW/[email protected] | gpg --import
Both ways work. That's what I had been doing. Only drawback is that the 
Build-Pkg "fails" to build modules as it discovers no module support.
It might look like only being cosmetic, but it prevents the script from 
building a linux26 package. Sure I can pick the kernel from /boot/vmlinuz, 
but it is only a workaround.

If I configured all necessary ROCKCFGSET_ parameters then I feel that 
Build-Pkg should not try to build modules in the case the kernel doesn't 
support modules.

_______________________________________________
rock-user mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-user

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBDZ2TJs2JwJnQ6UqcRAmP6AKCv/sfNbrNEcIzKpcDDWvu7fUYDbwCeKpgS
V5M9c3QgauFXRtNZho0T1so=
=TA+J
-----END PGP SIGNATURE-----