> On Jun 4, 2019, at 13:40, Alejandro Hernandez
> <[email protected]> wrote:
>
> Multiconfig should not have anything to do with this,
> I'm not exactly sure what you are running into, since I'm not able to
> reproduce it
> but I don't see why those directories would exist, I would try cleaning as
> well and that will probably fix it.
>
>
> Also, once we release the warrior branch, pmu-firmware should work with
> master and warrior (from oe-core) just fine,
> and there will be a small change on the way multiconfig is setup to make it
> faster.
>
> Cheers,
>
> Alejandro
Hi Alejandro,
Thanks for your help.
Check my last reply. It was this
https://github.com/Xilinx/meta-xilinx/blob/64aa3d35ae9e612355677d1fb8d06143be06d92e/meta-xilinx-standalone/recipes-standalone/pmu-firmware/pmu-firmware_2018.3.bb#L28
from master which I had from a bad merge with 2019.1 that caused the error.
You guys should check this from my last reply though:
> So 6aa787afce5ae454ce0a072fbf93e47e3960ada1 should have also removed the
> mention of xsecure_sha2_pmu.a. Also, copy_bsp.sh should have "set -e" at the
> top so it fails if the script fails one of its steps.
Cheers!
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx
