[Buildroot] [PATCH 6/6] apply-patches.sh: use series file to apply patches in proper order

Ludovic Desroches ludovic.desroches at atmel.com
Wed Mar 21 10:05:10 UTC 2012


On Wed, Mar 21, 2012 at 10:02:43AM +0100, Peter Korsgaard wrote:
> >>>>> "Ludovic" == Ludovic Desroches <ludovic.desroches at atmel.com> writes:
> 
>  Ludovic> Thanks to take this set of patches.
> 
> I'm afraid I'll have to revert patch 5+6 unless we can fix it up though,
> as the tarball change broke the build for (atleast) liblockfile:
> 
> http://buildroot.humanoidz.org/results/cf2f653df3e083b75d3f8d0f4020a68100588d2d/build-end.log
> 
> The patch tarball contains:
> 
> .
> └── debian
>     ├── changelog
>     ├── control
>     ├── patches
>     │   ├── 02-COPYRIGHT.patch
>     │   ├── 04-505851-remove-debug-code.patch
>     │   ├── 06-493462-dotlockfile.1.patch
>     │   ├── 07-493462-dotlockfile.c.patch
>     │   ├── 09-562937-make-ar-overwrittable.patch
>     │   └── series
>     ├── postinst
>     ├── postinst.nfs
>     ├── postrm
>     ├── prerm.nfs
>     ├── rules
>     ├── shlibs
>     ├── shlibs.nfslock
>     └── source
>         ├── format
>         └── options
> 

I was afraid by this kind of tarball. Nightmare becomes real!

> I guess it worked more by accident than anything else before, but I
> think we should atleast ensure we only apply files matching
> *.{patch,diff} inside the tarballs.
> 
> I don't have a problem with having to add a specific post-patch hook for
> liblockfile similar to E.G. argus, but we need to get it to work.
> 
> Care to have a look?

I will have a look o this issue

Regards

Ludovic



More information about the buildroot mailing list