I understand this - I've done it more than once.  The problem persists.

Tks, R


----- Original Message -----
From: "Andy Ross" <[EMAIL PROTECTED]>
To: "FlightGear developers discussions" <[EMAIL PROTECTED]>
Sent: Wednesday, November 05, 2003 9:54 PM
Subject: Re: [Flightgear-devel] Re: Compliation of CVS -Source Error BEHOLD
etc


> Richard Hornby wrote:
> > The test-up error message (ref undefined reference) refers to a line
> > in /math/point3d.hxx which does not look as if it contains anything
> > to do with the problem.
>
> I give 100:1 odds this means you have two versions of SimGear
> installed to different places.  The one being picked up at compile
> time by the FlightGear configure script is the wrong version.
>
> What I do is to use a custom --prefix in the configure scripts.  I
> never, ever install development stuff into /usr/local.  Specifically,
> my FlightGear build trees go into /home/andy/fg.  So modulo typos and
> general email oopsen, this will work to build a complete FlightGear
> from scratch:
>
> cd /home/andy/fg
>
> #
> # Download and build plib:
> #
> cvs -d -d:pserver:[EMAIL PROTECTED]:/cvsroot/plib login
> cvs -d -d:pserver:[EMAIL PROTECTED]:/cvsroot/plib co plib
> cd plib
> ./autogen.sh
> ./configure --prefix=/home/andy/fg
> make
> make install
> cd ..
>
> #
> # Download and build SimGear:
> #
> # (This presumes you already have a working Metakit installation.  I
> #  don't install metakit globally on my machine either, but that's
> #  because I'm paranoid; it's always been very stable across FlightGear
> #  releases.)
> #
> cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.2 login
> cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/SimGear-0.2 co SimGear
> cd SimGear
> ./autogen.sh
> ./configure --prefix=/home/andy/fg
> make
> make install
> cd ..
>
> #
> # Download and build FlightGear:
> #
> cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login
> cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co
> source
> cd source
> ./configure --prefix=/home/andy/fg
> make
> make install
> cd ..
>
> #
> # Finally download the FlightGear base package, and fix up a link from
> # the "lib" directory.  (Or just rename the data directory to
> # "lib/FlightGear", whatever)
> #
> cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 co
data
> cd lib
> ln -s ../data FlightGear
> cd ..
>
> #
> # And run:
> #
> bin/fgfs
>
> ==
>
> You now have a working development version of FlightGear that you can
> hack to your hearts content without fear that it will pollute (or be
> polluted by) other junk on the system.  When you break something, or
> stuff gets confused, or you just don't want it any more you can just
> blow it all away and start over.  No regrets, no worries.
>
> Andy
>
>
>
> _______________________________________________
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
>



_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to