Re: [Flightgear-devel] Still linker error in today's FlightGear

2003-03-21 Thread Erik Hofman
Jonathan Polley wrote: In my case, I don't want any of the multi-pilot code in my build. For some reason, as of yesterday, src/MultiPlayer is required for the build (--with-network is defaulted to yes). If it requires that I build with --with-network-olk then this is a very bad thing

Re: [Flightgear-devel] Still linker error in today's FlightGear

2003-03-21 Thread Martin Spott
Erik Hofman [EMAIL PROTECTED] wrote: A fix is in CVS now. Not bad Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! --

[Flightgear-devel] Still linker error in today's FlightGear

2003-03-20 Thread Martin Spott
Hello, today I encountered linker errors on SuSE-8.1/i386. As I understand this does not depend on the tool chain: make[2]: Wechsel in das Verzeichnis »/usr/local/src/FlightGear/src/Main« g++ -DPKGLIBDIR=\/usr/local/FlightGear/lib/FlightGear\ -O3 -D_REENTRANT -L/usr/local/lib -L/opt/gnu/lib -s

Re: [Flightgear-devel] Still linker error in today's FlightGear

2003-03-20 Thread Erik Hofman
Martin Spott wrote: Hello, today I encountered linker errors on SuSE-8.1/i386. As I understand this does not depend on the tool chain: Did you already try this: You will either have to do a make clean or remove the following files by hand: Cockpit/hud.o GUI/gui.o GUI/gui_funcs.o Main/main.o

Re: [Flightgear-devel] Still linker error in today's FlightGear

2003-03-20 Thread Martin Spott
Hello Erik, Erik Hofman [EMAIL PROTECTED] wrote: Martin Spott wrote: Hello, today I encountered linker errors on SuSE-8.1/i386. As I understand this does not depend on the tool chain: Did you already try this: You will either have to do a make clean or remove the following files by

Re: [Flightgear-devel] Still linker error in today's FlightGear

2003-03-20 Thread Jonathan Polley
In my case, I don't want any of the multi-pilot code in my build. For some reason, as of yesterday, src/MultiPlayer is required for the build (--with-network is defaulted to yes). If it requires that I build with --with-network-olk then this is a very bad thing (IMHO) because I don't