Hi Juro,

My Yocto environment is for the Congatec QMX6 SoM that is built around a quadcore i.MX6. I use the Yocto layers from the Congatec repository (https://git.congatec.com/public), which includes the meta-fsl-arm and meta-fsl-arm-extra layers.

My bblayers.conf is:

  ${BSPDIR}/sources/poky/meta \
  ${BSPDIR}/sources/poky/meta-poky \
  ${BSPDIR}/sources/meta-openembedded/meta-oe \
  ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
  ${BSPDIR}/sources/meta-openembedded/meta-python \
  ${BSPDIR}/sources/meta-openembedded/meta-networking \
  ${BSPDIR}/sources/meta-fsl-arm \
  ${BSPDIR}/sources/meta-fsl-arm-extra \
  ${BSPDIR}/sources/meta-fsl-demos \
  ${BSPDIR}/sources/meta-mingw \
  ${BSPDIR}/sources/meta-peek \
  ${BSPDIR}/sources/meta-peek-ecng \

The image I normally build (peek-image-ecng-acu-default) is based upon the core-image-full-cmdline image.

I built the MinGW SDK by adding SDKMACHINE="x86_64-mingw32" to my local.conf and typing the command "bitbake peek-image-ecng-acu-default -c populate_sdk".

I attended the Yocto developer day in Berlin last week. When I showed the MinGW linker LTO plugin error to Mark Hatle, he suggested applying his patch.

best regards,


Bystricky, Juro schreef op 14.10.2016 20:04:
Could you please elaborate on what do you mean by "built it as-is".
I tested the meta layer with some cases I considered typical
or most common. (I think I enumerated them in my original
message). Apparently I missed one.



-----Original Message-----
From: Winfried [mailto:winfried_...@xmsnet.nl]
Sent: Friday, October 14, 2016 10:26 AM
To: yocto@yoctoproject.org
Cc: Bystricky, Juro <juro.bystri...@intel.com>
Subject: [meta-mingw] Patch needed to let linker find lto plugin

Recently the meta-mingw layer was updated to krogoth by Juro Bystricky.
Thanks !
However when I build it as-is, the linker fails because it can't load
the lto plugin.

After applying commit a06e473590207f72b11d273a09de2c8a889c381e from
meta-mingw-contrib (by Mark Hatle), the error disappeared.


W. Dobbe
yocto mailing list

Reply via email to