Bug 769993 - please backport d2daaa1eb6deaa17f6c9bc110cf7d927d8dcd767
Summary: please backport d2daaa1eb6deaa17f6c9bc110cf7d927d8dcd767
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-22 23:05 UTC by Rafael Ávila de Espíndola
Modified: 2016-11-24 15:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-29 09:50:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rafael Ávila de Espíndola 2011-12-22 23:05:51 UTC
Without that commit the macro __extern_inline can be used without being defined:


$ cat test.cpp
#include <fenv.h>
$ /usr/bin/clang++ -c test.cpp  -O
In file included from test.cpp:1:
In file included from /usr/include/fenv.h:58:
/usr/include/bits/fenv.h:105:1: error: unknown type name '__extern_inline'
__extern_inline int
^
/usr/include/bits/fenv.h:105:17: error: expected unqualified-id
__extern_inline int
                ^
2 errors generated.

Comment 1 Jeff Law 2011-12-23 05:29:49 UTC
Scheduled for the next build, 24.fc16.5.  24.fc16.4 is already in-flight.

Comment 2 Laurent Rineau 2012-02-09 13:18:05 UTC
When will it be built?

Comment 3 Jeff Law 2012-02-09 16:16:21 UTC
When I get the few hours I need to wrap up a follow-on fix to 552960.  Certainly within the next week or so.

Comment 4 Fedora Update System 2012-02-14 03:53:42 UTC
glibc-2.14.90-24.fc16.5 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/glibc-2.14.90-24.fc16.5

Comment 5 Fedora Admin XMLRPC Client 2013-01-28 20:08:20 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Laurent Rineau 2013-01-29 09:50:21 UTC
Anyway, that bug is already fixed!


Note You need to log in before you can comment on or make changes to this bug.