# X86 build broken with warrior-v2020-02

**URL:** <https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538>\
**Category:** General Discussions\
**Created:** [February 13, 2020, 7:56pm UTC](https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538 "2020-02-13T19:56:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\
**Post date:** [February 13, 2020, 7:56pm UTC](https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538/1 "2020-02-13T19:56:13Z")

</div>

Hi,

we start seeing issue with building mender for x86 machines (intelNUC) with meta-mender warrior-v2020-02 branch. When revert to warrior-v2019-12 build pass fine.  
Issue is:

```auto
bootfs.image_uefiimg/EFI/BOOT/bootx64.efi already exists in boot partition. Please verify that packages do not put files in the boot partition that conflict with IMAGE_BOOT_FILES.

```

and ` task do_image_uefiimg: Failed`

We don’t set `EFI_PROVIDER` in our local conf. I can see some changes regarding EFI\_PROVIDER was done between mentioned 2 tags. Thanks.

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [February 13, 2020, 10:49pm UTC](https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538/2 "2020-02-13T22:49:29Z")

</div>

Hi @MarekBelisko the EFI\_PROVIDER stuff was part of one of my PRs. Can you see if [https://github.com/drewmoseley/meta-mender/commit/2d59a8e00a1b3a4c1d5c95655c3a3a314e80e3c2](https://github.com/drewmoseley/meta-mender/commit/2d59a8e00a1b3a4c1d5c95655c3a3a314e80e3c2) resolves this issue for you?

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [February 14, 2020, 8:13am UTC](https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538/3 "2020-02-14T08:13:49Z")

</div>

I think this has come up before as well, so I have put it on my backlog to cherry-pick that commit. IIRC there were some conflicts regarding the tests, but it appears to be quite important to include this one.

---

<div class="post-metadata">

**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\
**Post date:** [February 14, 2020, 8:26am UTC](https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538/4 "2020-02-14T08:26:45Z")

</div>

@kacf @drewmoseley thanks for heads up. We currently stay on warrior-v2019-12 until we have this cherry-picked. 👍

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [February 18, 2020, 11:54am UTC](https://hub.mender.io/t/x86-build-broken-with-warrior-v2020-02/1538/5 "2020-02-18T11:54:22Z")

</div>

FYI, this has been cherry-picked and tagged now with `warrior-v2020.02.2`.