ltib
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] CVS broke my ltib? Or did it?

From: Robert S. Grimes
Subject: Re: [Ltib] CVS broke my ltib? Or did it?
Date: Fri, 20 Mar 2009 14:53:55 -0400 (EDT)
Hi Stuart,

Thanks for the info.  I don't have access to my dev machine right now, and I don't remember exactly what it was.  The link on Freescale's site referred to the mcf532x, but the ISO really supports both the mcf532x and mcf537x - apparently there's been effort to merge those two.

I will look into doing it myself next week, if I can figure out what to do.  I'm guessing it is pretty easy for someone experienced like yourself, but I don't know how to do that myself.  But, given that I expect it would be good for me to learn, I'm happy to at least look at it, and try my luck.

Have a great weekend!
-Bob

---- Original message ----

Date: Fri, 20 Mar 2009 17:31:45 +0000
From: Stuart Hughes <address@hidden>
Subject: Re: [Ltib] CVS broke my ltib?  Or did it?
>Hi Bob,
>
>There's 2 ways that can happen:
>
>1/ Freescale decide to merge it out.
>2/ Someone downloads the ISO and merges it to Savannah.
>
>I don't have the bandwidth to do #2 right now. If you have the ISO
>maybe it's something you could look at doing (all that's needed is the
>config/platform/_target_ and spec files for the kernel/u-boot). Quite
>possible the referenced content is already on bitshrine.org (this is
>more automated). If not, please send email to Freescale and ask them to
>push this out to Savannah.
>
>BTW: which platform is this, that is what's the name of the ISO image?
>
>Regards, Stuart
>
>On Fri, 2009-03-20 at 12:33 -0400, Robert S. Grimes wrote:
>> Hi Stuart,
>>
>> Yes, that fixed it just fine - thanks.
>>
>> By the way, one of the problems I was having with microwindows is the
>> framebuffer in the linux-v2.6.22-uc1, which does not support 320x240
>> LCD display resolution - it only supports 240x320. The newer
>> linux-2.6.26-uc0 kernel, which is in one of the Freescale ISO ltibs,
>> does support 320x240. Any idea when that'll work its way into CVS?
>>
>> Cheers,
>> -Bob
>> Robert S. Grimes
>>
>> RSG Associates
>> Embedded Systems and Software Development
>> for Military, Aerospace, Industry - and beyond!
>> 617.697.8579
>> www.rsgassoc.com
>>
>> email message attachment (Message 56.eml)
>> On Fri, 2009-03-20 at 12:33 -0400, Robert S. Grimes wrote:
>> > Thanks, Stuart - I'll try this tonight!
>> >
>> > Bob
>> >
>> > Sent from my Verizon Wireless BlackBerry
>> >
>> > -----Original Message-----
>> > From: Stuart Hughes <address@hidden>
>> >
>> > Date: Thu, 19 Mar 2009 14:05:42
>> > To: <address@hidden>
>> > Cc: <address@hidden>
>> > Subject: Re: [Ltib] CVS broke my ltib? Or did it?
>> >
>> >
>> > Hi Robert,
>> >
>> > I've checked in an update to CVS that will fix this. To use this do:
>> >
>> > $ cvs up
>> > $ ./ltib -c
>> >
>> > This will re-read the main.lkc file and compute the right kernel target
>> > to build.
>> >
>> > Here's the details:
>> >
>> > * The kconfig warnings from the kernel can be ignored, they will be
>> > fixed in later kernels: http://lkml.org/lkml/2007/5/19/221
>> >
>> > * The problem that cause the build failure was happening as
>> > kernel-common.tmpl has been updated to build uImage for m68knommu as a
>> > default now. For this platform there was no override placed in main.lkc
>> > to correctly build for the BSP. I've updated
>> > config/platform/m532xevb/main.lkc
>> >
>> > @@ -143,6 +138,17 @@
>> > default "kernel-2.6.22-uc1" if KERNEL3
>> > default "kernel26-dir-build" if KERNEL_DIR_BUILD
>> >
>> > +# if later someone adds u-boot kernels, then
>> > +# add entries for those kernels before the defaults
>> > +# for SYSCFG_KTARG and SYSCFG_BOOT_KERNEL
>> > +config SYSCFG_KTARG
>> > + string
>> > + default "vmlinux"
>> > +
>> > +config SYSCFG_BOOT_KERNEL
>> > + string
>> > + default "vmlinux"
>> > +
>> > source ../../userspace/kernel_dir_build.lkc
>> >
>> > Regards, Stuart
>> >
>> > On Thu, 2009-03-19 at 10:26 +0000, Stuart Hughes wrote:
>> > > Hi Robert,
>> > >
>> > > I've just merged the latest to Savannah. If that platform's defconfig
>> > > gets updated, it will update your copy and possibly that's why you had
>> > > problems (initially).
>> > >
>> > > I'll see if I can figure out what's wrong with a clean check-out.
>> > >
>> > > Regards, Stuart
>> > >
>> > > On Wed, 2009-03-18 at 21:42 -0400, Robert S. Grimes wrote:
>> > > > Hi,
>> > > >
>> > > > I did a CVS update today, and now I cannot get ltib to run. Even after
>> > > > a "./ltib -m distclean", running "./ltib -c" fails. Here is the tail of
>> > > > the console output:
>> > > >
>> > > > ...
>> > > > #
>> > > > # configuration written to .config
>> > > > #
>> > > > +
>> > > > [ -f /home/rsg/ltib/config/platform/m532xevb/linux-2.6.22.config ]
>> > > > + diff
>> > > > -q ./.config /home/rsg/ltib/config/platform/m532xevb/linux-2.6.22.config
>> > > > Files ./.config
>> > > > and /home/rsg/ltib/config/platform/m532xevb/linux-2.6.22.config
>> > > > differ
>> > > > + cp
>> > > > -f ./.config /home/rsg/ltib/config/platform/m532xevb/linux-2.6.22.config.dev
>> > > > + [ -n ]
>> > > > + [ %{kernel_series} = 2.4 ]
>> > > > + make ARCH=m68knommu HOSTCC=ccache /usr/bin/gcc -B/usr/bin/
>> > > > uImage
>> > > > scripts/kconfig/conf -s arch/m68knommu/Kconfig
>> > > > drivers/macintosh/Kconfig:116:warning: 'select' used by config
>> > > > symbol 'PMAC_APM_EMU' refers to undefined symbol 'APM_EMULATION'
>> > > > make: *** No rule to make target `uImage'. Stop.
>> > > > error: Bad exit status from /home/rsg/ltib/tmp/rpm-tmp.35223 (%
>> > > > build)
>> > > >
>> > > >
>> > > > RPM build errors:
>> > > > Bad exit status from /home/rsg/ltib/tmp/rpm-tmp.35223 (%
>> > > > build)
>> > > > Build time for kernel-2.6.22-uc1: 9 seconds
>> > > >
>> > > > Failed building kernel-2.6.22-uc1
>> > > >
>> > > >
>> > > > f_buildrpms() returned an error, exiting
>> > > > traceback:
>> > > > main:557
>> > > >
>> > > >
>> > > > Started: Wed Mar 18 21:37:43 2009
>> > > > Ended: Wed Mar 18 21:38:45 2009
>> > > > Elapsed: 62 seconds
>> > > >
>> > > > These packages failed to build:
>> > > > kernel-2.6.22-uc1
>> > > >
>> > > > Build Failed
>> > > >
>> > > > $
>> > > >
>> > > > Any ideas what is broken, and how I broke it?
>> > > >
>> > > > Thanks,
>> > > > -Bob
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > _______________________________________________
>> > > > LTIB home page: http://bitshrine.org
>> > > >
>> > > > Ltib mailing list
>> > > > address@hidden
>> > > > http://lists.nongnu.org/mailman/listinfo/ltib
>> > > >
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > LTIB home page: http://bitshrine.org
>> > >
>> > > Ltib mailing list
>> > > address@hidden
>> > > http://lists.nongnu.org/mailman/listinfo/ltib
>> > >
>> >
>> >
>> >
>> > _______________________________________________
>> > LTIB home page: http://bitshrine.org
>> >
>> > Ltib mailing list
>> > address@hidden
>> > http://lists.nongnu.org/mailman/listinfo/ltib
>> > _______________________________________________
>> > LTIB home page: http://bitshrine.org
>> >
>> > Ltib mailing list
>> > address@hidden
>> > http://lists.nongnu.org/mailman/listinfo/ltib
>> _______________________________________________
>> LTIB home page: http://bitshrine.org
>>
>> Ltib mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/ltib
>

Robert S. Grimes

RSG Associates
Embedded Systems and Software Development
for Military, Aerospace, Industry - and beyond!
617.697.8579
www.rsgassoc.com
reply via email to
[Prev in Thread] Current Thread [Next in Thread]