It doesn't make sense to me because neither line 331, nor the line you cited 
has string in them. 
Moreover, line 13 of wizard.h reads "using std::string;" 

Are you sure your sources of fgrun are current and you don't have an old 
wizard.h elsewhere ? 

Regards, 
-Fred 

----- "Harry Campigli" a écrit : 
> Thanks Csaba 
> 
> Sorry I must have been in error copying line 331 to the post incorrectly. 
> 
> Any how : Puttting adding namespace std; in the wizard.h file as I saw 
> someone suggest for fgrun elsewhere works around the problem. 
> 
> On Sat, Feb 19, 2011 at 10:49 PM, Csaba Halász < csaba.hal...@gmail.com > 
> wrote: 
> 


> On Sat, Feb 19, 2011 at 2:28 PM, Harry Campigli < harryc...@gmail.com > 
> wrote: 
> > 
> > I find issues with building FGrun on Ubuntu 10:10 FG and SG are both 
> > current from the git repostories FG run is v1.5.2 
> > 
> > Make stops with: 
> > In file included from wizard.cxx:7: 
> > wizard.h:331: error: ‘string’ does not name a type 
> > make[2]: *** [wizard.o] Error 1 
> > 
> > wizard.h line 331 is : 
> > 
> > FlightGearThread *fgThread; 
> 
> Sounds like you are looking at the wrong file/line, since that line 
> doesn't have "string" on it. 
> 
> 
> > Is this an issue from compiling fgrun to the git version of FG? 
> 
> This is a problem in fgrun, it is missing #include <string> and/or it 
> has problem with properly referencing the namespace. 
> 

-- 
Frédéric Bouvier 
http://www.youtube.com/user/fgfred64 Videos 

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to