<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>8840</bug_id>
          
          <creation_ts>2015-12-18 19:19:12 +0000</creation_ts>
          <short_desc>Failure to build 32 bit eSDK on a 64 bit host</short_desc>
          <delta_ts>2020-05-28 08:12:37 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>devtools / tool chain</component>
          <version>2.1</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Low</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>Future</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Juro Bystricky">juro.bystricky</reporter>
          <assigned_to name="Unassigned">unassigned</assigned_to>
          <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>randy.e.witt</cc>
    
    <cc>randy.macleod</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>57395</commentid>
    <comment_count>0</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-12-18 19:19:12 +0000</bug_when>
    <thetext>When running

$ bitbake core-image-sato -c populate_sdk_ext

on a 64 bit host, with the SDKMACHINE=&quot;i686&quot;

we get an error:

ERROR: The extensible SDK can currently only be built for the same architecture as the machine being built on - SDK_ARCH is set to i686 (likely via setting SDKMACHINE) which is different from the architecture of the build machine (x86_64). Unable to continue.
ERROR: Function failed: do_populate_sdk_ext
ERROR: Logfile of failure stored in: /data/swat/poky/build-mastersdk-exe/tmp/work/qemuppc-poky-linux/core-image-sato/1.0-r0/temp/log.do_populate_sdk_ext.20509
ERROR: Task 12 (/data/swat/poky/meta/recipes-sato/images/core-image-sato.bb, do_populate_sdk_ext) failed with exit code &apos;1&apos;

The point is, we get this error AFTER the core-image-sato was built, which can take a loooong time. Unless this is just a temporary limitation, this should be addressed, otherwise there will be some disgruntled users.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>58930</commentid>
    <comment_count>1</comment_count>
    <who name="Randy Witt">randy.e.witt</who>
    <bug_when>2016-02-11 21:25:04 +0000</bug_when>
    <thetext>*** Bug 8929 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80298</commentid>
    <comment_count>2</comment_count>
    <who name="Paul Eggleton">bluelightning</who>
    <bug_when>2018-04-18 15:06:00 +0000</bug_when>
    <thetext>The problem here is that we don&apos;t have a convenient mechanism for disabling individual tasks in a manner such that an error is shown if they are called (similar to SkipRecipe for entire recipes). However, Richard suggests a possible workaround in the form of deleting the do_populate_sdk_ext task in anonymous python and then re-creating it as a task with no dependencies that shows an appropriate error - in that case that task would be able to be scheduled early in the build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>87355</commentid>
    <comment_count>3</comment_count>
    <who name="Randy MacLeod">randy.macleod</who>
    <bug_when>2020-05-28 08:12:37 +0000</bug_when>
    <thetext>Too many technical significant challenges involved.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>