RE: [Ltib] Add a new platform to LTIB

[Stuart Hughes]

Hi Colin,

Glad you found the problem with config ARMEABI_ARCH.

Yes you can have a vanilla kernel.  To do this, create a spec file in
dist/lfs-5.1/kernel that only has a source tarball and no patches.  For
example, you could do this:

$ cp dist/lfs-5.1/kernel/kernel-2.6.20.spec.in 
dist/lfs-5.1/kernel/kernel-2.6.27.spec.in

and then edit it and change the version 2.6.27.  You'd then need to make
sure you have that tarball in /opt/ltib/pkgs.

When you've done that in your config/platform/_target_/main.lkc in the
kernel section, add your kernel to the choice list:

+    config KERNEL2
+        bool "Linux 2.6.27"
+        help
+           vanilla kernel.org 2.6.27

and then add it to the PKG_KERNEL section, this is what ties the package
to the spec file (which is different to the normal pkg_map entry).  So
for example:

config PKG_KERNEL
    string
    default "kernel-2.6.22-mx" if KERNEL1
+    default "kernel-2.6.27" if KERNEL2
    default "kernel26-dir-build" if KERNEL_DIR_BUILD


Regards, Stuart

On Wed, 2008-12-17 at 10:00 +0000, Colin Helliwell wrote:
> Hi Stuart,
> [see follow-up below!]
> Still having a few problems setting up for a new target. I've done the
> required changes to main.lkc (and commented out the CPU section). Deleted
> .config* and defconfig.dev, the defconfig file is a copy from the IMX27ADS.
> I then do a ltib -m distclean (to make sure) and the ltib --configure.
> I can choose my new target in the first screen, I exit and save, then the
> second config screen comes up. Noticeable problem is that the toolchain
> settings (e.g. flags) are blank - if I save and exit then it complains that
> TOOLCHAIN_PREFIX and TOOLCHAIN_PATH aren't set. Indeed, looking in the
> resulting .config file there is just a single (blank)
> "CONFIG_TOOLCHAIN_CFLAGS" setting in this section.
> I can't see why this target isn't pulling in the correct files/settings? 
> 
> ****  ****
> OK, follow up before I've even sent the mail: The cause of the problem seems
> to be that my platform was not included in the "default y if .." line of the
> "config ARMEABI_ARCH" section of userspace/defaults.lkc
> This has fixed it.
> ****  ****
> 
> 
> Next question: I'm not sure what I should be doing about PKG_KERNEL for my
> new target. I'm not aware (yet) of any patching I need to do, so really I'd
> just like it to set up to use the latest vanilla kernel - is this possible?
> 
> Thanks.
> 
>