Re: [Ltib] Working with Freescale 8323

[Stuart Hughes]

Hi Charles,

You should not be using -f, this means force and should (hardly ever) be
used.

If you changed something in the source tree, then the kernel should
rebuild.  All you need to incant is: ./ltib (or maybe ./ltib -p kernel
at most).  If it does not re-build after a change, then that's a bug and
with a test-case can be fixed (are you using any funky file system? or
options?)

So far as shell/make go, this can work, but it's advanced and you'd need
to mimic how the .spec file does the kernel build.  Probably much
simpler to let ltib take care of that.

Regards, Stuart

On 04/02/11 16:24, Charles Krinke wrote:
> Thank you Peter for your help.
> 
> I thought I was out of the woods last night, but this morning, I ended
> up with a very similar issue I started with. Yesterday, I was able to do
> "./ltib -f -p kernel -m scbuild" with no problem.
> 
> Then I edited a c source file and a found that ./ltib -f -p kernel -m
> scbuild did not rebuild the edited source file. Looked like ltib could
> not tell the time stamp changed.
> 
> So, .... in my zeal, I went "./ltib -m shell" and
> cd/rpm.BUILD/linux-2.6.20 and executed a make.
> 
> At this point, make fails (and subsequent invocations of ./ltib -f -p
> kernel -m scbuild also fail) with a error on scripts/basic/fixdep.
> 
> Using "file", I can see that scripts/basic/fixdep is a PPC executable
> and not a host executable, so I end up very confused.
> 
> I *thought* that the cross compiler setup was already handled in the
> ltib shell so this must be some environment issue.
> 
> What I am trying to use is the ltib from Freescale to get back to a
> baseline. This particular ltib is dated 20081112 so is older then
> current state-of-the-ltib. But the issue is that it should be possible
> to go back to an ltib iso image from 1, 2 or 4 years ago and be able to
> work with it to compile u-boot, kernel and a root filesystem. At least
> that is what I have told my customer. So, until I gain a bit more
> understanding, I am a bit behind the eight-ball, so to speak.
> 
> Charles
> 
> On Thu, Feb 3, 2011 at 5:20 PM, Peter Barada <address@hidden
> <mailto:address@hidden>> wrote:
> 
>     On 02/03/2011 07:52 PM, Charles Krinke wrote:
>>     I got the ltib running for the 8323 on two different computers,
>>     but had to go through the ltib configure step several times and
>>     eventually found the right combination of settings that lets me be
>>     able to build u-boot, uImage and rootfs.jffs2.
>>
>>     This leads to another question. "What is the location of the
>>     configure file and its name that ./ltib --configure creates?".
>>
>>     I think I need to study this file a bit *and* another engineer
>>     that I am supporting wants to get the same ltib running and
>>     already requested the configuration file at which point I had to
>>     shrug, look foolish and say "dunno where it is yet".
>     You'll find it in config/platform/<platform>/.config, created from
>     config/platform/defconfig.dev (and if that doesn't exist then
>     config/platform/defconfig.dev).  the defconfig.dev and .config in
>     the config/platform/<platform>/ directory are created from the
>     config/platform/<platform>/defconfig which is the default
>     configuration you use when you use "./ltib" unless you change the
>     configuration with "./tlib -c" or "./ltib --configure"....
> 
> 
> 
> 
> _______________________________________________
> LTIB home page: http://ltib.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib