KLarsen <kroy...@gmail.com> [2010-03-18 14:07:58]:
> Thank you Petr. I've tried changing the SRCREV variable to
> "ac07af55554567b6226ba8dd623756c630e93103" but when I do this, there
> is a compile error about undefined references to a few variables.
I wonder if you can do that easily by just changing SRCREV, but I don't think
so. You would need to revert state of whole(maybe just few recipes, dirs) OE
back to the revision where there was
SRCREV="ac07af55554567b6226ba8dd623756c630e93103" in linux-omap-psp_2.6.32.bb.
Then it might build.
Well, the current SRCREV is older (Nov '09) than this new (Feb '10)
"ac07af5555..." SRCREV that I've changed it to. So I don't think a
linux-omap-psp_2.6.32.bb has ever been committed where
SRCREV="ac07af55554567b6226ba8dd623756c630e93103". But then again,
they could have gone back to the older sources for some other reason.
> thinking that Koen (the guy who made the Angstrom demo image) has
> added more patches to recipes/linux/linux-omap-psp-2.6.32.bb to get it
> to compile and has not yet committed them to the repository. He has
> also changed recipes/linux/linux-omap-psp_2.6.32/beagleboard/defconfig
> as the configuration in the demo uImage is not the same as that in OE
> git.
Yes, he's evil guy, just blame him! 
Haha! Aren't all developers evil? 
> Oh well, hopefully he pushes those changes out sometime.
No, you need to go back in time with OE to build that kernel revision and have same
defconfig. BTW, why do you need just that particular revision?
I'd just like to start from a known good configuration. I know that
the demo image works very well for me so I would be nice to start by
recompiling it exactly before making any changes.
But speaking of going back in time, I'm new to git. What would be the
easiest way to find out if SRCREV was ever equal to
"ac07af55554567b6226ba8dd623756c630e93103"?
-Kameron