<?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>8214</bug_id>
          
          <creation_ts>2015-08-27 01:58:19 +0000</creation_ts>
          <short_desc>glibc build failure with DEBUG_BUILD = &quot;1&quot;</short_desc>
          <delta_ts>2015-10-26 12:36:30 +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>core</component>
          <version>1.8</version>
          <rep_platform>x86</rep_platform>
          <op_sys>x86</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>2.0</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Steven Walter">stevenrwalter</reporter>
          <assigned_to name="Juro Bystricky">juro.bystricky</assigned_to>
          <cc>bogdanx.a.voiculescu</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>raj.khem</cc>
    
    <cc>randy.e.witt</cc>
    
    <cc>sgw</cc>
    
    <cc>stevenrwalter</cc>
          
          <qa_contact name="Bogdan Alexandru Voiculescu">bogdanx.a.voiculescu</qa_contact>
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>53461</commentid>
    <comment_count>0</comment_count>
    <who name="Steven Walter">stevenrwalter</who>
    <bug_when>2015-08-27 01:58:19 +0000</bug_when>
    <thetext>Building on Ubuntu 14.04 x86_64.  Configured for MACHINE = qemux86 and SDKMACHINE = i686.  Running &quot;bitbake glibc&quot; fails in glibc with this compile error:

| In file included from ../sysdeps/i386/tlsdesc.c:25:0:
| ../include/inline-hashtab.h: In function &apos;_dl_make_tlsdesc_dynamic&apos;:
| ./tlsdeschtab.h:28:1: error: inlining failed in call to &apos;hash_tlsdesc&apos;: indirect function call with a ye
t undetermined callee [-Werror=inline]
|  hash_tlsdesc (void *p)
|  ^
[...]
| cc1: all warnings being treated as errors
| make[2]: *** [/mnt/storage/poky/build/tmp/work/i586-poky-linux/glibc/2.21-r0/build-i586-poky-linux/elf/t
lsdesc.os] Error 1</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53462</commentid>
    <comment_count>1</comment_count>
    <who name="Steven Walter">stevenrwalter</who>
    <bug_when>2015-08-27 02:09:47 +0000</bug_when>
    <thetext>DEBUG_BUILD = &quot;1&quot; is also necessary for the failure to occur.  SDKMACHINE = i686 without DEBUG_BUILD = &quot;1&quot; succeeds.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53463</commentid>
    <comment_count>2</comment_count>
    <who name="Randy Witt">randy.e.witt</who>
    <bug_when>2015-08-27 02:41:32 +0000</bug_when>
    <thetext>I tested this in my ubuntu container and it also happened when using qemux86-64 with DEBUG_BUILD = &quot;1&quot;. I left SDKMACHINE at the default, I don&apos;t believe SDKMACHINE has an effect on this issue.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53470</commentid>
    <comment_count>3</comment_count>
    <who name="Steven Walter">stevenrwalter</who>
    <bug_when>2015-08-27 12:28:02 +0000</bug_when>
    <thetext>Agreed, I can reproduce this with only DEBUG_BUILD = &quot;1&quot;.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53497</commentid>
    <comment_count>4</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-08-27 15:50:17 +0000</bug_when>
    <thetext>Seems to be already fixed with the commit:
625e0ec8b5e5f1c39b3bfad0e6adfecaf957d689

(I will verify this)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53501</commentid>
    <comment_count>5</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-08-27 17:02:03 +0000</bug_when>
    <thetext>So yes, it&apos;s been fixed with 1.9 (tested with master commit 393bd7496d71eb101f21234c1233a2d18fd2c73e)

glibc builds OK, you get a notification:

NOTE: glibc can&apos;t be built with -O, -O -Wno-error will be used instead.

Will try to cherry pick the commit 625e0ec8b5e5f1c39b3bfad0e6adfecaf957d689
and apply it to Fido (1.8).</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53504</commentid>
    <comment_count>6</comment_count>
    <who name="Steven Walter">stevenrwalter</who>
    <bug_when>2015-08-27 17:18:17 +0000</bug_when>
    <thetext>Cherry-picking that commit onto the fido branch doesn&apos;t help for me.  I still get the same fatal warning on tlsdesc.os.  I do get the NOTE about using -Wno-error during parse time, but my log.do_compile still shows the -Werror flag being used.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53505</commentid>
    <comment_count>7</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-08-27 17:22:37 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; Cherry-picking that commit onto the fido branch doesn&apos;t help for me.  I
&gt; still get the same fatal warning on tlsdesc.os.  I do get the NOTE about
&gt; using -Wno-error during parse time, but my log.do_compile still shows the
&gt; -Werror flag being used.

Thanks. I will have a closer look. Apparently it needs cherry-picking something else as well.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53506</commentid>
    <comment_count>8</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-08-27 19:21:02 +0000</bug_when>
    <thetext>(In reply to comment #7)
&gt; (In reply to comment #6)
&gt; &gt; Cherry-picking that commit onto the fido branch doesn&apos;t help for me.  I
&gt; &gt; still get the same fatal warning on tlsdesc.os.  I do get the NOTE about
&gt; &gt; using -Wno-error during parse time, but my log.do_compile still shows the
&gt; &gt; -Werror flag being used.
&gt; 
&gt; Thanks. I will have a closer look. Apparently it needs cherry-picking
&gt; something else as well.

So this commit needs to be back ported as well:
d6a2cf3cbef581478185c25d8a7a6109a201c583</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53507</commentid>
    <comment_count>9</comment_count>
    <who name="Steven Walter">stevenrwalter</who>
    <bug_when>2015-08-27 19:46:26 +0000</bug_when>
    <thetext>(In reply to comment #8)
&gt; (In reply to comment #7)
&gt; &gt; (In reply to comment #6)
&gt; &gt; &gt; Cherry-picking that commit onto the fido branch doesn&apos;t help for me.  I
&gt; &gt; &gt; still get the same fatal warning on tlsdesc.os.  I do get the NOTE about
&gt; &gt; &gt; using -Wno-error during parse time, but my log.do_compile still shows the
&gt; &gt; &gt; -Werror flag being used.
&gt; &gt; 
&gt; &gt; Thanks. I will have a closer look. Apparently it needs cherry-picking
&gt; &gt; something else as well.
&gt; 
&gt; So this commit needs to be back ported as well:
&gt; d6a2cf3cbef581478185c25d8a7a6109a201c583

Unless I&apos;m mistaken, that commit is already present in the fido branch</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53508</commentid>
    <comment_count>10</comment_count>
    <who name="Steven Walter">stevenrwalter</who>
    <bug_when>2015-08-27 19:56:52 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; Cherry-picking that commit onto the fido branch doesn&apos;t help for me.  I
&gt; still get the same fatal warning on tlsdesc.os.  I do get the NOTE about
&gt; using -Wno-error during parse time, but my log.do_compile still shows the
&gt; -Werror flag being used.

My bad, that commit does in fact fix the issue.  I have a glibc bbappend in one of my layers that must have been defeating the fix.  It works in a stock poky build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>53544</commentid>
    <comment_count>11</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-08-28 20:57:59 +0000</bug_when>
    <thetext>So it turns out only the commit 625e0ec8b5e5f1c39b3bfad0e6adfecaf957d689: “glibc: Consider adding -Wno-error in cases when not using -O2”

needs to be backported to Fido.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>54844</commentid>
    <comment_count>12</comment_count>
    <who name="Juro Bystricky">juro.bystricky</who>
    <bug_when>2015-09-30 17:49:00 +0000</bug_when>
    <thetext>Commit backported to Fido:

https://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=fido&amp;qt=grep&amp;q=Consider+adding+-Wno-error+in+cases+when+not+using+-O2</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>55734</commentid>
    <comment_count>13</comment_count>
    <who name="Bogdan Alexandru Voiculescu">bogdanx.a.voiculescu</who>
    <bug_when>2015-10-26 12:36:30 +0000</bug_when>
    <thetext>Verified on master: 505a82673ac2487df5ea343a6422c2fc47018831
and on fido: fido:fa55b8e5050c6d7a47ef8e9bc213d0cc9471b43a</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>