[oe] Strange do_patch behaviour
Dmitry Vinokurov
d.vinokuroff at gmail.com
Thu Aug 27 12:04:19 UTC 2009
Chris Conroy wrote:
> On Wed, 2009-08-26 at 19:33 +0600, Dmitry Vinokurov wrote:
>
>> ------------
>> And looks like bitbake did nothing except patching, but actually it does
>> (diff between manually and bitbake patched dirs is ~30000 strings, and I
>> decided not to attach it:)) and as a result builded kernel fails with
>> kernel panic. Diff shows, that '.pc' dir is created (and some files in
>> it are forbidden for any access (0000 rights)) and not only it -- some
>> other files like in arch/arm or sound/soc/lpc3xxx/ differs too. Tried to
>> remove tmp/ and rebuild -- same result.
>>
>> Could anybody explain this strange behaviour? I thought that patch task
>> should only execute 'patch' command.
>>
>>
>
> Bitbake uses a tool called 'quilt' in order to do the patching, and
> quilt creates the .pc directory. Basically, quilt lets you deal with
> patches as a stack. If you go into the linux work directory, you should
> be able to run quilt commands to manually figure out what OE is patching
> here.
>
> 'quilt applied' to see what patches are applied
> 'quilt pop' to pop a patch off the stack
> 'quilt push' to push a patch onto the stack.
>
> Some Quilt Links:
> Very helpful presentation: http://www.coffeebreaks.org/blogs/wp-content/archives/talks/2005/quilt/quiltintro-s5.html
> Overview PDF: http://www.suse.de/~agruen/quilt.pdf
> Savannah page: http://savannah.nongnu.org/projects/quilt
>
Thanks, refs and information was really helpful. Actually the only
differences were in .pc and patches/, the only one applied patch was my
phy3250. I just was inattentive and confused strings with differences in
files and strings with file names.
--
Best Regards,
Dmitry Vinokurov
<d.vinokuroff at gmail.com>
More information about the Openembedded-devel
mailing list