On 05-06-17 14:12, Jean-Francois Dagenais wrote:
On Jun 2, 2017, at 16:03, Manjukumar Harthikote Matha
<[email protected]> wrote:
Yes we are aware of this issue, this will happen only if you have built the
firmware successfully before. If it is a clean project it would fail during
do_deploy mechanism.
This depends on a clean state, something that is not respectful of Yocto's
normal behaviour. Plus it falsely fail at do_deploy, which is completely
misleading.
In the short term, as Mike suggests, the compile step could start by removing
the output from it's workdir, then test it's presence at the end. I will see
about making a patch for this.
If the task only fails at do_deploy, then Yocto would only retry that
step, without calling do_compile again because that did not fail, and
keep failing at deploy over and over again until some frustrated human
intervenes and clears the sstate cache or in some other way makes the
compile re-run.
In other words, it really needs fixing.
--
Mike Looijmans
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: [email protected]
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
Join our presentation at Electronics & Applications 2017:
FPGA for real-time data processing, subject “Hardware platform for industrial
ultrasound steel plate Inspection” Topic Embedded Systems - Herman Kuster, 1st
June 10 AM
Visit http://eabeurs.nl/author/612884/ for more information
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx
