On 25 April 2018 at 09:59, ChenQi wrote:
> After checking it again, I think removing the '/' would be sufficient.
>
> do_unpack[cleandirs] = "${@d.getVar('S') if d.getVar('S') !=
> d.getVar('WORKDIR') else os.path.join('${S}', 'patches')}"
To protect against this I'm running a test build with thi
On 25 April 2018 at 11:00, Burton, Ross wrote:
> Good work Chen, the trailing slash was making me wonder but I didn't
> check. Best normalise both of those paths before comparing.
Yeah, I will make that change and we will see in a couple of days if
still produces any errors.
--
Med Vänliga Häl
Good work Chen, the trailing slash was making me wonder but I didn't
check. Best normalise both of those paths before comparing.
Ross
On 25 April 2018 at 09:59, ChenQi wrote:
> After checking it again, I think removing the '/' would be sufficient.
>
> do_unpack[cleandirs] = "${@d.getVar('S') if
On 25 April 2018 at 10:39, Burton, Ross wrote:
> Is the build tree deleted after it fails? It would be interesting to
> see if the compiler is present in the sysroot, or if it has a
> different name, or something else weird.
Isn't it weird that it does not have a log for "prepare_recipe_sysroot?
After checking it again, I think removing the '/' would be sufficient.
do_unpack[cleandirs] = "${@d.getVar('S') if d.getVar('S') !=
d.getVar('WORKDIR') else os.path.join('${S}', 'patches')}"
Best Regards,
Chen Qi
On 04/25/2018 04:38 PM, Burton, Ross wrote:
Plenty of recipes do that though...
On 25 April 2018 at 10:39, Burton, Ross wrote:
> Is the build tree deleted after it fails? It would be interesting to
> see if the compiler is present in the sysroot, or if it has a
> different name, or something else weird.
I have lost the "state" tinkering around, but before I did that
checked
Is the build tree deleted after it fails? It would be interesting to
see if the compiler is present in the sysroot, or if it has a
different name, or something else weird.
Do you have any global classes that do anything interesting/special?
Ross
On 25 April 2018 at 09:24, Mirza Krak wrote:
> H
Plenty of recipes do that though...
On 25 April 2018 at 09:36, ChenQi wrote:
> I guess the problem is caused by the following line.
>
> S = "${WORKDIR}/"
>
> Try setting it to some dir under ${WORKDIR}, and make sure source file is
> under it.
> Check if the problem is still there after the above
I guess the problem is caused by the following line.
S = "${WORKDIR}/"
Try setting it to some dir under ${WORKDIR}, and make sure source file
is under it.
Check if the problem is still there after the above change.
Best Regards,
Chen Qi
On 04/25/2018 04:24 PM, Mirza Krak wrote:
Hi.
I have
Hi.
I have come across a somewhat strange error that I can not explain to
my self, why it is occurring and hopefully someone on the list can
provide some insight.
I am currently on "rocko" on all my layers and the recipe that I
having issues with is brcm-patchram-plus[1]. And even though this
rec
10 matches
Mail list logo
