Bug 56079 - Non-standard C++ code
Summary: Non-standard C++ code
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: freetype
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike A. Harris
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-12 16:48 UTC by Bernhard Rosenkraenzer
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-11-12 16:48:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Bernhard Rosenkraenzer 2001-11-12 16:48:16 UTC
Description of Problem:
ttmkfdir uses non-standards compilant C++ code, causing it to fail with 
gcc 3.1

Version-Release number of selected component (if applicable):
2.0.5-1

How Reproducible:
100%

Steps to Reproduce:
1. rpm --rebuild freetype-2.0.5-1.src.rpm

Actual Results:
g++ -Wall -pedantic -I../freetype-pre1.4/lib/. -ggdb -c ttmkfdir.cpp  
-fPIC -DPIC -o .libs/ttmkfdir.lo
In file included from ttmkfdir.h:6,
                 from ttmkfdir.cpp:6:
commandline.h:11: warning: ISO C++ forbids declaration of `ostream' with 
no
   type
commandline.h:11: `ostream' is neither function nor member function; 
cannot be
   declared friend
commandline.h:11: parse error before `&' token
commandline.h:12: warning: ISO C++ forbids declaration of `ostream' with 
no
   type
commandline.h:12: `ostream' is neither function nor member function; 
cannot be
   declared friend
commandline.h:12: declaration of `int Commandline::ostream'
commandline.h:11: conflicts with previous declaration `int 
Commandline::ostream
   '
commandline.h:12: parse error before `&' token
commandline.h:12: duplicate member `Commandline::ostream'
In file included from ttmkfdir.cpp:7:
ttf.h:34: parse error before `&' token


Expected Results:
package builds

Additional Information:
STL classes live in the std namespace these days; adding "using namespace 
std;" will probably be sufficient to fix this.

Comment 1 Bernhard Rosenkraenzer 2001-11-12 16:56:24 UTC
I've fixed it in 2.0.5-2.



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