Bug 467172 - glibc header signalfd.h error:expected initializer before ‘throw’
Summary: glibc header signalfd.h error:expected initializer before ‘throw’
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-16 07:57 UTC by Parag AN(पराग)
Modified: 2008-10-20 09:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-20 09:56:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Parag AN(पराग) 2008-10-16 07:57:19 UTC
Description of problem:
When any simple C++ file which includes <sys/signalfd.h> headers then its compilation fails with error
/usr/include/sys/signalfd.h:54: error: expected initializer before ‘throw’

Reference:-
While reviewing new package fbterm #465928 , I see above compilation problem. 

Version-Release number of selected component (if applicable):
glibc-2.8.90-13.fc10

How reproducible:
always

Steps to Reproduce:
1. compile source code 
---------------------------------------
#include <iostream>
#include <sys/signalfd.h>
using namespace std;
int main()
{
cout<<"Testing Throw";
return 0;
}
----------------------------------------
2. observe error
3.
  
Actual results:
/usr/include/sys/signalfd.h:54: error: expected initializer before ‘throw’

Expected results:
It should not report error.

Additional info:
I am not sure if this is correct to report bug to fix compilation error.
The solution I see is as
---------------------------------
#include <iostream>
#undef __THROW
#define __THROW
#include <sys/signalfd.h>
using namespace std;
int main()
{
cout<<"Testing Throw";
return 0;
}
--------------------------------

Comment 1 Jakub Jelinek 2008-10-20 09:56:33 UTC
Should be fixed in glibc-2.8.90-14 in rawhide.


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