[Flightgear-devel] linking errors with origin/next?

2012-02-11 Thread Scott Hamilton
  

I updated my git working directory to origin/next and am getting
the following link errors, I'm not 100% sure that git is properly
updating everything, I have done a make clean and make rebuild_cache
on both simgear and flightgear. 
Is anyone else seeing these errors, or
is my working directory really messed up? 

Linking CXX executable fgfs 


CMakeFiles/fgfs.dir/globals.cxx.o: In function
`FGGlobals::set_fg_root(std::basic_string const)': 

/src/Flightgear/git-repo/flightgear/src/Main/globals.cxx:220: undefined
reference to `SGPath::realpath() const'


CMakeFiles/fgfs.dir/globals.cxx.o: In function
`FGGlobals::append_aircraft_path(std::basic_string const)':

/src/Flightgear/git-repo/flightgear/src/Main/globals.cxx:306: undefined
reference to `SGPath::realpath() const'


CMakeFiles/fgfs.dir/globals.cxx.o: In function
`FGGlobals::append_fg_scenery(std::basic_string const)':

/src/Flightgear/git-repo/flightgear/src/Main/globals.cxx:256: undefined
reference to `SGPath::realpath() const'

../Airports/libfgAirports.a(groundnetwork.cxx.o): In function
`FGGroundNetwork::render(bool)':


/src/Flightgear/git-repo/flightgear/src/Airports/groundnetwork.cxx:1439:
undefined reference to `SGMaterial::get_effect()'


/src/Flightgear/git-repo/flightgear/src/Airports/groundnetwork.cxx:1513:
undefined reference to `SGMaterial::get_effect()'

../ATC/libfgATC.a(trafficcontrol.cxx.o): In function
`FGStartupController::render(bool)':


/src/Flightgear/git-repo/flightgear/src/ATC/trafficcontrol.cxx:1412:
undefined reference to `SGMaterial::get_effect()'

/src/Flightgear/git-repo/flightgear/src/ATC/trafficcontrol.cxx:1489:
undefined reference to `SGMaterial::get_effect()' 
collect2: ld returned
1 exit status 
make[2]: *** [src/Main/fgfs] Error 1 
make[1]: ***
[src/Main/CMakeFiles/fgfs.dir/all] Error 2 
make: *** [all] Error 2 

 --
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] linking errors with origin/next?

2012-02-11 Thread ThorstenB
Am 11.02.2012 10:16, schrieb Scott Hamilton:
 I updated my git working directory to origin/next and am getting the
 following link errors, I'm not 100% sure that git is properly updating
 everything, I have done a make clean and make rebuild_cache on both
 simgear and flightgear.
 Is anyone else seeing these errors, or is my working directory really
 messed up?

Looks like a local problem on your machine.

You can always check with the build server:
http://flightgear.simpits.org:8080/

If you're having a compile or link problem, but the lights for your 
platform are all green there (i.e. Windows/Linux/Mac, Release or Next), 
then you're very likely to have local issue.

cheers,
Thorsten

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] linking errors with origin/next?

2012-02-11 Thread Scott

thanks Thorsten,

  Now to find out why, must be a static link library somewhere that
isn't getting updated...


  cheers
  S.




On Sat, 2012-02-11 at 11:24 +0100, ThorstenB wrote:
 Am 11.02.2012 10:16, schrieb Scott Hamilton:
  I updated my git working directory to origin/next and am getting the
  following link errors, I'm not 100% sure that git is properly updating
  everything, I have done a make clean and make rebuild_cache on both
  simgear and flightgear.
  Is anyone else seeing these errors, or is my working directory really
  messed up?
 
 Looks like a local problem on your machine.
 
 You can always check with the build server:
 http://flightgear.simpits.org:8080/
 
 If you're having a compile or link problem, but the lights for your 
 platform are all green there (i.e. Windows/Linux/Mac, Release or Next), 
 then you're very likely to have local issue.
 
 cheers,
 Thorsten
 
 --
 Virtualization  Cloud Management Using Capacity Planning
 Cloud computing makes use of virtualization - but cloud computing 
 also focuses on allowing computing to be delivered as a service.
 http://www.accelacomm.com/jaw/sfnl/114/51521223/
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel



--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] linking errors with origin/next?

2012-02-11 Thread Adrian Musceac
On Saturday, February 11, 2012 14:01:55 Scott wrote:
 thanks Thorsten,
 
   Now to find out why, must be a static link library somewhere that
 isn't getting updated...
 
 
   cheers
   S.
 

Hi,

I had the same problem recently, and it took me quite a long while to figure 
it out. It may be the same for you or not, but I think it's worth mentioning 
this just in case: if you build simgear and flightgear with 
CMAKE_BUILD_TYPE=Debug, libraries have a d suffix. If afterwards you 
switch flightgear to Release and forget to do the same for simgear, 
flightgear tries to link to old Release simgear libraries which don't have a 
d suffix. Of course, the right way to do this is to have separate build 
trees for build types, like it's described in the cmake readme, but of course 
I did not follow this procedure and was bitten by this issue. Worst part was 
flooding the tracker with fake bug reports and pestering Thorsten because of 
my local issue :)
I still have a common build tree, but now I check the flags beforehand.

Cheers,
Adrian

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel