<?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>6534</bug_id>
          
          <creation_ts>2014-07-14 22:18:02 +0000</creation_ts>
          <short_desc>Does the Yocto Project toolchain support &apos;multilib&apos; (within the toolchain)?</short_desc>
          <delta_ts>2014-12-11 16:29:50 +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>1.7</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>INVALID</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>1.7</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="baoshan">pangbw</reporter>
          <assigned_to name="Mark Hatle">mark.hatle</assigned_to>
          <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>44477</commentid>
    <comment_count>0</comment_count>
    <who name="baoshan">pangbw</who>
    <bug_when>2014-07-14 22:18:02 +0000</bug_when>
    <thetext>I am trying to build gcc-cross in &apos;multilib&apos; mode under Yocto, I have tried many methods but without luck, I looked into the code and feel the &apos;multilib&apos; is NOT supported at all though we can find some receipt files in the Yocto source tree. 

Can someone tell me if &apos;multilib&apos; is supported or not at this point? If it is, please give me a simple steps to show how to do that.

Thanks,
Baoshan</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>44538</commentid>
    <comment_count>1</comment_count>
    <who name="Mark Hatle">mark.hatle</who>
    <bug_when>2014-07-17 14:54:32 +0000</bug_when>
    <thetext>There are two difference concepts of the multilib within the Yocto Project.

The primary usage is multiple toolchains (one per multilib) and multilib sysroots (again one per multilib).


&apos;gcc-cross&apos; does not support multilib configuration from what I understand.  The question should really be about gcc-cross-canadian (this is the toolchain that is located within the generated SDK.)


I believe the question is -- how are multilibs, within GCC enabled and used?  My understanding is that baoshan wants to generate an SDK that uses a single gcc binary with multilibs enabled.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>47518</commentid>
    <comment_count>2</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2014-12-11 16:29:50 +0000</bug_when>
    <thetext>If the question is whether we plan to make gcc-cross support multilib, we do not, that isn&apos;t the way multilib support in OE works. This isn&apos;t something we plan to change and the bug resolution would be WONTFIX.

On the other hand, our builds do support multilib, as do our SDK and gcc-cross-canadian and so on so that would be WORKSFORME.

If there is a specific issue to address please open a new bug or reopen this with the details.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>