ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltib] Linux Kernel Source Code post patched -> where?


From: John Jeffers
Subject: [Ltib] Linux Kernel Source Code post patched -> where?
Date: Tue, 08 Apr 2008 13:11:33 -0500
User-agent: Thunderbird 2.0.0.12 (X11/20080226)

Stewart

>"So if you have /usr/src/linux/.config if you look at this on you host >you'll actually be seeing the kernel config file for your host >machine."

By the way I cleaned out the symlink so /usr/src/linux is not used by the host sources. Ltib asked for rights to use it (ie. it failed naming rights there as the problem). There is as I said no source left in there. (I changed the name of the host symlink to linux-link so I can put it back.)

>"The correct way to interpret this would be if you looked on your >target board. In this case, if you'd selected to install the kernel >source, you'd see the right thing."

in "/home/jjeffers/projects/ltib-mcf5445x-20071214/rootfs/usr/src" there are just include (.h) files......


I have read the FAQ and I see the package sources. (And am reading all the past ltib questions as well.)

BUT I want the kernel sources post-patched that we build from.  I am
reading the perl script.

While I have told the --config control [x] leave source.  I see
elsewhere where ltib cleaned the source in the terminal. (And I am trying to locate this in the script.)

1) Where should the kernel source go! (did I miss it?  Or is Ltib Dec 07
incorrect?)

2) Does the leave source option mean kernel source? (I should think so.)

3) Building on openSuSE 10.3, "Dec 2007 m54455 BSP iso".  The build is
successful.

FYI on openSuSE iso's mount as /media/<volume name> automagically. If one names the iso "m54444 BSP" for example the volume name has a space in it. Ltib script does not like a space in the name. For the future I would suggest Freescale does not put a space in iso volume names and instead puts a hyphen to avoid this issue.

Thanks ahead of time!

John







reply via email to

[Prev in Thread] Current Thread [Next in Thread]