Curtis L. Olson wrote:
Well you could run an "updatedb" as root so your find database is
current and then try typing things like "locate newbucket.hxx" or
"locate constants.hxx" or "locate libsgbucket"
You should find versions of these in your source tree, but if you see
these (or any of the other simgear files) showing up, you need to go
get rid of them.
The locate command isn't necessarily fool proof depending on your
system configuration, so even if it doesn't turn up any matches, that
doesn't necessarily mean you are out of the woods (again depending on
your system configuration.)
Just to be clear, you need to remove all hints of simgear from
/usr/lib/libsg* /usr/include/simgear /usr/local/lib/libsg*
/usr/local/include/simgear and any other locations you might have tried
installing it.
Then you need to decide if you are going to build
SimGear-0.3.8/FlightGear-0.9.8 or SimGear-cvs/FlightGear-cvs
Pick the correct version of simgear and build/install it so that this
version is the only version on your system. Then you should be able to
build the corresponding version of FlightGear.
If you still have problems similar to what you are reporting, then I
would be 99.9% confident that you have some stray version of simgear
floating around or are mixing wrong versions of FG/SG or have some other
mix of wierdness left over from trying a bunch of things that is
confusing the build.
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
