Discussion:
[Ltib] Forcing kernel rebuild
Petteri Matilainen
2014-02-17 08:47:29 UTC
Permalink
Hi,

I've been using LTIB for my embedded Freescale platform. The entire
build system was pre-packaged and set up. It works fine, however
recently I've noticed that even if I change something in the kernel
config, the resulting kernel image doesn't have the same config. For
example, I've been playing with SPI and sometimes I turn on the option
SPI debugging. When enabled, I see debugging messages during boot-up.
Last time I turned the option off and rebuild the kernel (ltib -m
config -> config kernel and after that just run ltib) I still got the
debug messages at boot-up.

For kernel image, I'm using the vmlinux.bin found at <ltib
dir>/rpm/BUILD/linux-2.6.38/arch/m68k/boot. Deleting the kernel tree
is not an option because I have modified the sources. Ltib version
9.1.1, Revision 1.453.

I have also tried the --force option but that doesn't work for kernel.
Is there any way to force just the kernel rebuild? Or, if anyone has
ideas why the kernel image is not what it's supposed to be? Thanks.

- Pete
Jump, Lance
2014-02-17 11:12:35 UTC
Permalink
Designation: Non-Finmeccanica

Pete,

How are you changing the kernel config? Are you doing it using LTIB, or are you doing it directly in the kernel build directory? You should use LTIB because it maintains a kernel configuration file in config/platform/<platformType>. That file ends up getting copied to the kernel build directory. If you make changes without using LTIB, the modified kernel config file will not get copied back to the LTIB config tree and you will effectively lose your changes.

Lance
-----Original Message-----
Sent: Monday, February 17, 2014 3:47 AM
Subject: [Ltib] Forcing kernel rebuild
Hi,
I've been using LTIB for my embedded Freescale platform. The entire
build system was pre-packaged and set up. It works fine, however
recently I've noticed that even if I change something in the kernel
config, the resulting kernel image doesn't have the same config. For
example, I've been playing with SPI and sometimes I turn on the option
SPI debugging. When enabled, I see debugging messages during boot-up.
Last time I turned the option off and rebuild the kernel (ltib -m
config -> config kernel and after that just run ltib) I still got the
debug messages at boot-up.
For kernel image, I'm using the vmlinux.bin found at <ltib
dir>/rpm/BUILD/linux-2.6.38/arch/m68k/boot. Deleting the kernel tree
is not an option because I have modified the sources. Ltib version
9.1.1, Revision 1.453.
I have also tried the --force option but that doesn't work for kernel.
Is there any way to force just the kernel rebuild? Or, if anyone has
ideas why the kernel image is not what it's supposed to be? Thanks.
- Pete
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
https://lists.nongnu.org/mailman/listinfo/ltib
3.3.042312
Peter Barada
2014-02-17 15:01:56 UTC
Permalink
Post by Petteri Matilainen
Hi,
I've been using LTIB for my embedded Freescale platform. The entire
build system was pre-packaged and set up. It works fine, however
recently I've noticed that even if I change something in the kernel
config, the resulting kernel image doesn't have the same config. For
example, I've been playing with SPI and sometimes I turn on the option
SPI debugging. When enabled, I see debugging messages during boot-up.
Last time I turned the option off and rebuild the kernel (ltib -m
config -> config kernel and after that just run ltib) I still got the
debug messages at boot-up.
You can run "./ltib -p kernel -c" to run the config step for the kernel,
build it, install it, build any dependent packages, and then deploy the
target image.
Post by Petteri Matilainen
For kernel image, I'm using the vmlinux.bin found at <ltib
dir>/rpm/BUILD/linux-2.6.38/arch/m68k/boot. Deleting the kernel tree
is not an option because I have modified the sources. Ltib version
9.1.1, Revision 1.453.
I have also tried the --force option but that doesn't work for kernel.
Is there any way to force just the kernel rebuild? Or, if anyone has
ideas why the kernel image is not what it's supposed to be? Thanks.
--force does indeed force a package to build, including the kernel...
Post by Petteri Matilainen
- Pete
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
https://lists.nongnu.org/mailman/listinfo/ltib
Continue reading on narkive:
Loading...