<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: S32G BSP Build error with using yocto in S32G</title>
    <link>https://community.nxp.com/t5/S32G/S32G-BSP-Build-error-with-using-yocto/m-p/1530548#M1479</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You should erase everything about yocto and restart again, this issue is very common when happens this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Thu, 29 Sep 2022 14:56:01 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2022-09-29T14:56:01Z</dc:date>
    <item>
      <title>S32G BSP Build error with using yocto</title>
      <link>https://community.nxp.com/t5/S32G/S32G-BSP-Build-error-with-using-yocto/m-p/1530107#M1468</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; When using&amp;nbsp;bitbake fsl-image-auto, buiding yocto bsp error，pionting out :&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; The postinstall intercept hook "update_font_cache" /"update_gtk_icon_cache"&amp;nbsp; failed&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; detail info is this:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (1) update_gtk_icon_cache&amp;nbsp;ERROR&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;NOTE: Running intercept scripts:&lt;BR /&gt;NOTE: &amp;gt; Executing update_gtk_icon_cache intercept ...&lt;BR /&gt;NOTE: Exit code 127. Output:&lt;BR /&gt;/home/cks/s32g/fsl-auto-yocto-bsp/build_s32g274aevb/tmp/work/s32g274aevb-fsl-linux/fsl-image-base/1.0-r0/intercept_scripts-18c2e18def091e750d3f1e16960804e8d4b4dc4ec55ce1a3bd63e990e798e5f9/update_gtk_icon_cache: 10: /home/cks/s32g/fsl-auto-yocto-bsp/build_s32g274aevb/tmp/work/s32g274aevb-fsl-linux/fsl-image-base/1.0-r0/intercept_scripts-18c2e18def091e750d3f1e16960804e8d4b4dc4ec55ce1a3bd63e990e798e5f9/update_gtk_icon_cache: /home/cks/s32g/fsl-auto-yocto-bsp/build_s32g274aevb/tmp/work/s32g274aevb-fsl-linux/fsl-image-base/1.0-r0/recipe-sysroot-native//gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: not found&lt;/P&gt;&lt;P&gt;ERROR: The postinstall intercept hook 'update_gtk_icon_cache' failed, details in /home/cks/s32g/fsl-auto-yocto-bsp/build_s32g274aevb/tmp/work/s32g274aevb-fsl-linux/fsl-image-base/1.0-r0/temp/log.do_rootfs&lt;BR /&gt;DEBUG: Python function do_rootfs finished&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (2)update_font_cache ERROR&lt;/P&gt;&lt;P&gt;ERROR: The postinstall intercept hook 'update_font_cache' failed, details in /home/cks/s32g/fsl-auto-yocto-bsp/build_s32g274aevb/tmp/work/s32g274aevb-fsl-linux/fsl-image-auto/1.0-r0/temp/log.do_rootfs&lt;BR /&gt;DEBUG: Python function do_rootfs finished.&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2022 06:12:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G-BSP-Build-error-with-using-yocto/m-p/1530107#M1468</guid>
      <dc:creator>ChenXiang</dc:creator>
      <dc:date>2022-09-29T06:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: S32G BSP Build error with using yocto</title>
      <link>https://community.nxp.com/t5/S32G/S32G-BSP-Build-error-with-using-yocto/m-p/1530548#M1479</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You should erase everything about yocto and restart again, this issue is very common when happens this.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2022 14:56:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G-BSP-Build-error-with-using-yocto/m-p/1530548#M1479</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-09-29T14:56:01Z</dc:date>
    </item>
  </channel>
</rss>

