On Fri, May 17, 2013 at 12:51:37PM +0200, Mike Looijmans wrote: > On 05/17/2013 12:15 PM, Martin Jansa wrote: > > On Fri, May 17, 2013 at 11:43:22AM +0200, Mike Looijmans wrote: > >> > >> I got this very weird build failure. It builds fine for one machine > >> (zedboard), but it craps out in a really weird way on the "zynq-zc702" > >> machine. > >> > >> Somehow the "package_write_ipk" task wants to find files in a directory > >> with "1-r0" (a version that has once existed a long long time ago) in > >> the version part, instead of the proper git hashed name. > >> > >> I've tried a "cleansstate" but that did not help. The "compile" step in > >> this recipe takes about 1,5 hour on my i7 system, so debugging this > >> recipe is painfully slow... > >> > >> I've attached the recipes, pasted the log below. > > > > try it with 2/2 patch from > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4102 > > > > I somehow fail to extract the patch from the mail correctly (probably > lack of skilz on my side, I am not often at the receiving end of mailed > patches).
Patchwork makes it a lot easier: http://patchwork.openembedded.org/patch/47329/ > But my recipe does mess with the PV string because the Xilinx tools will > fail to work properly when there is a "+" sign in the path. I'll try to > fix it in a more proper way than using a python replace, see if that helps. It could be caused by something else, just the error message looks the same when your recipe was built with different PV in different architecture before (that's what referenced patch detects and shows better error message then "No such file" later). -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
