Re: [Flightgear-devel] Runway plow
Andy wrote: >Jim Wilson wrote: > > Noticed that the c310 has its wheels below pavement. Is it ok to > > readjust the models for a recent change or is this a temporary? Or am > > I the only one > >Which FDM? There are three (count 'em) descriptions of where the >Cessna 310 wheels are relative to the aircraft coordinate origin -- >the model's, JSBSim's, and YASim's. My guess is that none of them >agree. Regarding the models coordinates, there is a way to do it without trial and error for every plane, see my homepage. I am just in the process of cleaning up and of looking into 0.79 and the current cvs version in this regard. I will be done by the weekend and announce here. If you can not wait: 1. My description omits that you have to press "3" before creating the ppeloc 2. By error, the ppeloc is written into the qhull directory 3. I am still investigating whether the new fgfs versions have the model in another spatial place than old versions. Old versions had magic numbers 5 degress and 1.61 z-offset that you had to subtract from the real values to get the FGFS values. Does anyone know whether they changed? What units are the vertex coordinates in? Meters? Feet? Just yesterday I recreated the "measuring rod" I use to measure fgfs to get these magic numbers. If people are interested, i can publish it. BTW, FWIW, if you import *.MDL models directly into fgfs, which is possible with 0.79 (and was not possible when I started my homepage), then they are smooth. >Andy Bye bye, Wolfram. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Metakit
> My computer crashed totally yesterday, and I sent it to be replaced (luckily > it was still under warranty). I either think it's RAM or the slot on the > motherboard for the RAM. Go find the MEMCHK project and download the floppy disk image. Copy it to a floppy and leave it running overnight (or over weekend, etc). It'll tell you for-sure what the status of your memory chips and bus are. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Metakit
Sorry Guys, The problem isn't with Metakit My computer crashed totally yesterday, and I sent it to be replaced (luckily it was still under warranty). I either think it's RAM or the slot on the motherboard for the RAM. Sorry to have taken your time. Danie Heath I build using RH 7.1, among others, and had no problem building Metakit. I unpacked the archive to my home directory and did the standard make and make install. What kind of errors are you seeing? Jonathan On Wednesday, March 6, 2002, at 10:09 AM, Martin Dressler wrote: > I'm not RH user, but why you don't try to install metakit from > distribution's rpm. In debian it work without problem. > > -- > Martin Dressler > > e-mail: [EMAIL PROTECTED] > http://www.musicabona.com/ > > ___ > 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 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Comms
> Dave Luff wrote: > > So supposing a pilot is communicating with approach on comm1, but has > > comm2 monitoring the tower, what happens if a stronger tower > > transmission is received at the same time as an approach transmission? > It doesn't have anything to do with signal strength. The two radios > receive the signals independently and provide a plain analog audio > output to the panel, which is essentially a mixer. Before we seriously confuse the RF people around here ... Andy means "mixer" as in the thing in your music system that combines sources. It _adds_ the two voltages together ... it does _NOT_ multiply them together. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
> I'm not sure any one has had flightgear running on a sun box in recent > memory. This means that whatever problems you have encountered > building on the solaris platform probably have been lurking for years [...] I _had_ a Solaris binary sometime summer 2000 using recent GCC and Solaris 'ld'. So it _was_ possible. Maybe it's still possible, but I don't have the time to verify by now. I promise that I'll try to fix the Solaris build process - but don't hold your breath, you might be waiting several weeks for it Even if I succeed in building a binary I won't be able to test it because it's only a four way Sparc20 without graphics board I'm running Solaris on, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS question
> Now that I am modifying code, I have the need to keep it updated. > I am a beginner at CVS, so I'm not sure I am doing things properly. > Should I be doing CVS updates every day? That requires that I > completely recompile and relink every day, is that correct? I want > to make sure that I am organizing thinks in a way that doesn't cause > me a lot of extra work at some point. Personally, when I'm working on something, I stop doing CVS updates because I want the code I'm developing against to be stable. However, when I've made progress, I grab a "cvs diff" to a separate file as a patch. Now that I've grabbed a context sensitive backup of my work, in case something terrible happens, I do the update and bring in everybody else's work. Then I look to see whether they broke what I was working on. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Ground Vehicles
> I got in touch with Curt a few days ago to try to get some help on > making Windows binaries for my project (Vamos Automotive Simulator I'm a non-windows developer, so I can't help. > Also, Curt suggested turning my ground vehicle model into a module for > FlightGear. The FAA has a real training problem with people whose job requires them to drive vehicles around airports. The ability to reuse the scenery, for both applications, and have trucks and aircraft, err, interact ... ... would probably go a long way towards meeting their needs. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Runway plow
Jim Wilson wrote: > Noticed that the c310 has its wheels below pavement. Is it ok to > readjust the models for a recent change or is this a temporary? Or am > I the only one Which FDM? There are three (count 'em) descriptions of where the Cessna 310 wheels are relative to the aircraft coordinate origin -- the model's, JSBSim's, and YASim's. My guess is that none of them agree. The only way to get this right is by brute force: check the descriptions for errors, figure out which is right by reference to ... something authoritative, and force them all to the same value while evading the inevitable unit and coordinate system convention differences. :) Even then, you'll need to put support for gear compression into the model description in order to have the wheels stay above ground. It's probably not as awful as I've made it sound, but it is tedious. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Runway plow
Noticed that the c310 has its wheels below pavement. Is it ok to readjust the models for a recent change or is this a temporary? Or am I the only one :-)? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] CVS question
> > A related question - after rebuilding with the makefile system, is > > there a way to "make install" only the files which have changed? For > > example, suppose there is only a change to a .cxx file in plib/ssg. I > > do a "make", which rebuilds only libplibssg.a. But when I do a "make > > install", all the header files are also installed with new dates. > > Are you sure? I was under the impression that the "install" program > (and CVS, for that matter) preserved the date stamps on files. The > stamps on the installed files should be the modification times in the > archive. I might be wrong... Andy, I checked the file modification dates and confirmed that "make install" does not preserve the dates on installed files (sure wish it did) at least on my Cygwin setup. Please correct me if I'm wrong, but the "make install" appears to use the script install-sh which is part of the automake package. The script is fairly complicated (to me) but buried in it is the cp command which does the actual installation. I think that the cp command is passed in using the make variable CPPROG. Perhaps the install-sh script (or the make variable) could be modified to use "cp -p" which preserves the file date and other attributes. Thanks to all who responded to my question! Paul Paul R. Deppe Veridian Engineering (formerly Calspan) Flight & Aerospace Research Group 150 North Airport Drive Buffalo, NY 14225 (716) 631-6898 (716) 631-6990 FAX [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Metakit
I build using RH 7.1, among others, and had no problem building Metakit. I unpacked the archive to my home directory and did the standard make and make install. What kind of errors are you seeing? Jonathan On Wednesday, March 6, 2002, at 10:09 AM, Martin Dressler wrote: > I'm not RH user, but why you don't try to install metakit from > distribution's rpm. In debian it work without problem. > > -- > Martin Dressler > > e-mail: [EMAIL PROTECTED] > http://www.musicabona.com/ > > ___ > 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
Re: [Flightgear-devel] CVS question
On Wednesday 06 March 2002 07:17 pm, you wrote: > quite the way you want them. One of the central characteristics of > being a geeky hacker type is a strongly held conviction that the rest > of the world are idiots and are doing things all wrong. :) > > Andy Hahahah! Quick somebody notify Bartletts ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS question
On Wed, Mar 06, 2002 at 05:17:42PM -0600, Curtis L. Olson wrote: > Paul Deppe writes: > > A related question - after rebuilding with the makefile system, is there a > > way to "make install" only the files which have changed? For example, > > suppose there is only a change to a .cxx file in plib/ssg. I do a "make", > > which rebuilds only libplibssg.a. But when I do a "make install", all the > > header files are also installed with new dates. Then when I rebuild SimGear > > and FlightGear, make thinks that the header files have changed and > > recompiles everything which depends on the header files (which is just about > > everything). This effect ripples down from plib to SimGear to FlightGear to > > Atlas. > > > > It would save a lot of compile time if one could "make install" only the > > files which have changed. Is there a way to do this? > > Beyond identifying and copying just the changed files individually > yourself by hand, I've never seen a way in unix to do this. > > If you know that there were changes only to a particular subdirectory, > you could cd into and run make; make install from there. You don't > have to run make or make install only from the top level directory. > That's one way you can often somewhat limit the number of changed > install files and contain the cascading dependency effect. > > Otherwise, it's a good time to go refill your cup of coffee or maybe > poke your head out into the living room and confirm to your family > that you still exist. (Expect some surprised looks the first few > times you do this though.) :-) You wouldn't have any personal experience, here, would you? ;-) > > Curt. > -- > Curtis Olson IVLab / HumanFIRST Program FlightGear Project > Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] > Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Tony Peden [EMAIL PROTECTED] We all know Linux is great ... it does infinite loops in 5 seconds. -- attributed to Linus Torvalds ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS question
Paul Deppe wrote: > A related question - after rebuilding with the makefile system, is > there a way to "make install" only the files which have changed? For > example, suppose there is only a change to a .cxx file in plib/ssg. I > do a "make", which rebuilds only libplibssg.a. But when I do a "make > install", all the header files are also installed with new dates. Are you sure? I was under the impression that the "install" program (and CVS, for that matter) preserved the date stamps on files. The stamps on the installed files should be the modification times in the archive. I might be wrong... > Then when I rebuild SimGear and FlightGear, make thinks that the > header files have changed and recompiles everything which depends on > the header files (which is just about everything). This effect > ripples down from plib to SimGear to FlightGear to Atlas. > > It would save a lot of compile time if one could "make install" only > the files which have changed. Is there a way to do this? The existing build stuff, frankly, is designed for the simple case where a user wants to compile and install something once for use in the future. If you're doing development, it's probably not optimal. A little elbow grease to match your private habits is probably unavoidable. For example, I always use a custom "--prefix" for all my FlightGear stuff, never install the shared metakit library, and often write 1-liner "build" "run" and "link" scripts for whatever focused feature I'm playing with. For your specific situation (if it turns out that timestamps really are your problem), you might try making symlinks from the install tree to the source tree, and skipping the "make install" step entirely. The core point being that you're never likely to find things packaged quite the way you want them. One of the central characteristics of being a geeky hacker type is a strongly held conviction that the rest of the world are idiots and are doing things all wrong. :) Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] CVS question
Paul Deppe writes: > A related question - after rebuilding with the makefile system, is there a > way to "make install" only the files which have changed? For example, > suppose there is only a change to a .cxx file in plib/ssg. I do a "make", > which rebuilds only libplibssg.a. But when I do a "make install", all the > header files are also installed with new dates. Then when I rebuild SimGear > and FlightGear, make thinks that the header files have changed and > recompiles everything which depends on the header files (which is just about > everything). This effect ripples down from plib to SimGear to FlightGear to > Atlas. > > It would save a lot of compile time if one could "make install" only the > files which have changed. Is there a way to do this? Beyond identifying and copying just the changed files individually yourself by hand, I've never seen a way in unix to do this. If you know that there were changes only to a particular subdirectory, you could cd into and run make; make install from there. You don't have to run make or make install only from the top level directory. That's one way you can often somewhat limit the number of changed install files and contain the cascading dependency effect. Otherwise, it's a good time to go refill your cup of coffee or maybe poke your head out into the living room and confirm to your family that you still exist. (Expect some surprised looks the first few times you do this though.) :-) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Ground Vehicles
Hi folks, I got in touch with Curt a few days ago to try to get some help on making Windows binaries for my project (Vamos Automotive Simulator http://vamos.sourceforge.net). He invited me to join the list to try to recruit some help. So drop me a line if FlightGear isn't keeping you busy enough:) Also, Curt suggested turning my ground vehicle model into a module for FlightGear. I don't have a lot of experience with programming graphics and sound, so using the FG framework might be a good way to go. If anyone has interest in helping me get started just let me know. I haven't gotten much in the way of feedback on Vamos, so if you decide to try it out I'd be interested in any impressions or suggestions you might have. Try driving the car really slowly; the engine sample might sound a little familiar:) Thanks. Sam ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] CVS question
> If you are using our unix style makefile system (automake/autoconf) > then it should track all the code dependencies and only rebuild code > that changes (or depends on something that has changed.) A related question - after rebuilding with the makefile system, is there a way to "make install" only the files which have changed? For example, suppose there is only a change to a .cxx file in plib/ssg. I do a "make", which rebuilds only libplibssg.a. But when I do a "make install", all the header files are also installed with new dates. Then when I rebuild SimGear and FlightGear, make thinks that the header files have changed and recompiles everything which depends on the header files (which is just about everything). This effect ripples down from plib to SimGear to FlightGear to Atlas. It would save a lot of compile time if one could "make install" only the files which have changed. Is there a way to do this? Thanks, Paul Paul R. Deppe Veridian Engineering (formerly Calspan) Flight & Aerospace Research Group 150 North Airport Drive Buffalo, NY 14225 (716) 631-6898 (716) 631-6990 FAX [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
Yes, all were built with gcc version 2.95.3. Salman On Wed, 6 Mar 2002 09:29:10 -0600 (CST) "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: > That looks really ugly ... could it be bugs/problems with the sun > linker? Have you tried building simple C++ programs with this same > version of gcc? Did you biuld plib, simgear, flightgear, etc. all > with the same compiler? > > Curt. > > > Salman Sheikh writes: > > Got that fixed. Now on file linking I get the following error: > > > > > > c++ -DPKGLIBDIR=\"/folks/salman/bin/lib/FlightGear\" -g -O2 >-L/folks/salman/bin/lib -o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o >fgfs.o globals.o options.o splash.o viewer.o viewer_lookat.o viewer_rph.o viewmgr.o >../../src/Aircraft/libAircraft.a../../src/ATC/libATC.a >../../src/Autopilot/libAutopilot.a ../../src/Cockpit/libCockpit.a >../../src/Controls/libControls.a../../src/FDM/libFlight.a >../../src/FDM/Balloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a >../../src/FDM/YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a >../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a >../../src/GUI/libGUI.a ../../src/Navaids/libNavaids.a >../../src/Scenery/libScenery.a ../../src/Sound/libSound.a >../../src/Airports/libAirports.a ../../src/Network/libNetwork.a >../../src/Objects/libObjects.a ../../src/Time/libTime.a >../../src/WeatherCM/libWeatherCM.a ../../src/Input/libInput.a -lsgroute >-lsgsky -lsgephem -lsgti! mi! > ng! > > -lsgio -lsgscreen -lsgmath -lsgbucket -lsgdebug -lsgmagvar -lsgmisc -lsgxml > -lsgserial -lplibpu -lplibfnt -lplibnet -lplibssg -lplibsg >-lmk4 -lz -L/space1/glut-3.7/lib/glut -lglut -lGLU -lGL -lXmu -lXt -lSM -lICE >-lXi -lXext -lX11 -lsocket -lpthread -lm -lplibul -lm > > ld: warning: relocation error: R_SPARC_32: file >../../src/Cockpit/libCockpit.a(hud_card.o): symbol .LLC238: > > external symbolic relocation against non-allocatable section .stab; > > cannot be processed at runtime: relocation ignored > > ld: warning: relocation error: R_SPARC_32: file >../../src/FDM/libFlight.a(LaRCsimIC.o): symbol .LLC155: > > external symbolic relocation against non-allocatable section .stab; > > cannot be processed at runtime: relocation ignored > > Undefined first referenced > > symbol in file > > slScheduler::playSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, >slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::~slScheduler(void) ../../src/Sound/libSound.a(soundmgr.o) > > slDSP::open(char *, int, int, int) ../../src/Sound/libSound.a(soundmgr.o) > > gethostbyname >../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > smMixer::smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > > slDSP::close(void) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::loopSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, >slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > > __slPendingError../../src/Sound/libSound.a(soundmgr.o) > > .LLC155 ../../src/FDM/libFlight.a(LaRCsimIC.o) > > gethostbyaddr >../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > slSample::autoMatch(slDSP *)../../src/Sound/libSound.a(soundmgr.o) > > inet_addr >/folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > slScheduler::init(void) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::stopSample(slSample *, int)../../src/Sound/libSound.a(soundmgr.o) > > .LLC238 ../../src/Cockpit/libCockpit.a(hud_card.o) > > inet_ntoa >/folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > smMixer::~smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::addSampleEnvelope(slSample *, int, int, slEnvelope *, >slEnvelopeType)../../src/Sound/libSound.a(soundmgr.o) > > slSample::loadFile(char *) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::realUpdate(int)../../src/Sound/libSound.a(soundmgr.o) > > ld: fatal: Symbol referencing errors. No output written to fgfs > > collect2: ld returned 1 exit status > > make: *** [fgfs] Error 1 > > > > > > > > > > > > On Tue, 5 Mar 2002 21:26:48 - > > "D Luff" <[EMAIL PROTECTED]> wrote: > > > > > Salman Sheikh writes: > > > > > > > Hello All, > > > > > > > > Got past the first error. Got a new one: > > > > > > > > Making all in NetworkOLK > > > > c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Inc
Re: [Flightgear-devel] CVS question
Boslough, Mark B writes: > Now that I am modifying code, I have the need to keep it updated. > I am a beginner at CVS, so I'm not sure I am doing things properly. > Should I be doing CVS updates every day? That requires that I > completely recompile and relink every day, is that correct? I want > to make sure that I am organizing thinks in a way that doesn't cause > me a lot of extra work at some point. Mark, There is a mailing list (flightgear-cvslogs) so you can get notified when ever the cvs repository has new changes committed to it. You may (or may not) want to take advantage of that depending on how closely you want to track what's going on. I'd think that if you ran cvs update once every day you'd be likely to get new changes just about time you ran it. Also, don't forget to check out a copy of the base package (via cvs) and run cvs update there as often as you run it on the source tree. If you are using our unix style makefile system (automake/autoconf) then it should track all the code dependencies and only rebuild code that changes (or depends on something that has changed.) Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS question
Hi Mark, What I do is update occaisonally (once or twice a week sometimes more) and keep an eye on the logs (the web based ViewCVS is handy too) in order to know what others are working on. Before sending in code I'll update to current CVS again and make sure things still work. It is much easier for Curt and Dave if you've taken care of any merges and send in code that works with latest CVS. Best, Jim "Boslough, Mark B" <[EMAIL PROTECTED]> said: > > Now that I am modifying code, I have the need to keep it updated. > I am a beginner at CVS, so I'm not sure I am doing things properly. > Should I be doing CVS updates every day? That requires that I > completely recompile and relink every day, is that correct? I want > to make sure that I am organizing thinks in a way that doesn't cause > me a lot of extra work at some point. > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] CVS question
Now that I am modifying code, I have the need to keep it updated. I am a beginner at CVS, so I'm not sure I am doing things properly. Should I be doing CVS updates every day? That requires that I completely recompile and relink every day, is that correct? I want to make sure that I am organizing thinks in a way that doesn't cause me a lot of extra work at some point. Thanks, Mark Boslough ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CC compiler problem?
Andy Ross wrote: > Erik Hofman wrote: > > Andy Ross wrote: > > > This is perfectly legal C++; I tried it with gcc (full program > > > attached) and it works fine. What errors are you seeing? > > > > This program gives me a core dump, because __fg_snd_[0].fn == NULL. > > Not in the code snippet you sent. The value of __fg_snd_[0].fn is the > address of the _fg_lin function. It's not my data structure, you > defined it. :) > > When run under gcc, in fact the _fg_lin function is called, and > returns zero, which output appears on the console. All normal. You > have a compiler bug. Which compiler are you using? Try sending the SGI MipsPro 7.2.1 > program to the vendor and saying "This is legal, gcc compiles it fine, > but you don't". Well, it is already an older version of the compiler which up until now hasn;t caused any problems. I think I have to check for bug fixes now. Thanks for the help Andy. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
Salman Sheikh writes: > Its a Sparc Ultra 60 with Elite3D card. > > Salman Salman, I'm not sure any one has had flightgear running on a sun box in recent memory. This means that whatever problems you have encountered building on the solaris platform probably have been lurking for years and you are the first to stumble on them. There are specific bugs and issues with the Irix linking process for instance which breaks down when building large C++ applications (but is ok for simple C++ linking.) We've had to come up with Irix specific 'hacks' to work around these problems. That's why I suggested that there could be bugs or limitations of the Solaris build tools (ar, ld, etc.) when building large C++ applications involving C++ libraries. Also, the messages you reported indicated that something earlier in the pipeline was generating code/instructions/symbols that something later in the pipeline couldn't understand. This smells to me like a bug somewhere in the build system (or a miscomunication between a gnu tool and a native sun tool in the compile pipeline.) For instance, gcc could be outputing symbols understood by the gnu ld, but not by the sun ld (?) I don't think you are running into a 'known' problem here (at least not known to the flightgear developers) and I don't know of any other solaris users on our developer list (let alone ones that have produced a successful fgfs build.) It may be that you are a bit on your own here and need to beat on this for a while yourself and find the solution on your own. Maybe there is some solaris/gcc mailing list where you could post your issues? It sounds like you need to locate some solaris compiler/building expertise. Once you do figure out what is going on, hopefully we can work the fix into the FlightGear build system so that future solaris users can benefit. That's probably not the answer you are looking for, but it's the best I can offer at this point (unless someone with solaris build experience can de-lurk and tell us all what is going on here.) Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
Its a Sparc Ultra 60 with Elite3D card. Salman On Wed, 6 Mar 2002 17:46:06 +0100 (MET) Martin Spott <[EMAIL PROTECTED]> wrote: > > > That looks really ugly ... could it be bugs/problems with the sun > > linker? > > Usually the sun assembler and linker - both in /usr/ccs/bin/ - are quite > fine with GCC. I've compiled more than 200 OpenSource packages using these > tools, so I believe you have to look somwhere else for this bug. > > After having a short look at the topic I have the impression that some > libraries might be missing at the linker command. On Solaris you will need > "-lsocket -lnsl" for binaries that do networking. > > Is this for Sparc or x86 ? I might have missed the message > > Martin. > -- > Unix _IS_ user friendly - it's just selective about who its friends are ! > -- > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > -- Salman Sheikh NASA/GSFC Code 564 Greenbelt, MD 20771 301-286-3763 301-286-0220 (fax) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CC compiler problem?
Erik Hofman wrote: > Andy Ross wrote: > > This is perfectly legal C++; I tried it with gcc (full program > > attached) and it works fine. What errors are you seeing? > > This program gives me a core dump, because __fg_snd_[0].fn == NULL. Not in the code snippet you sent. The value of __fg_snd_[0].fn is the address of the _fg_lin function. It's not my data structure, you defined it. :) When run under gcc, in fact the _fg_lin function is called, and returns zero, which output appears on the console. All normal. You have a compiler bug. Which compiler are you using? Try sending the program to the vendor and saying "This is legal, gcc compiles it fine, but you don't". Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CC compiler problem?
Andy Ross wrote: > Erik Hofman wrote: > > I have a propblem with a peace of CC code which is pretty standard for > > common C. When I define a structure and point an array to a > > pre-defined array; > > > > [...] > > > > this works for C but not for CC? Am I doing something wrong here, or > > doesn't CC allow this type of declaration (and if not, is there an > > alternative)? > > This is perfectly legal C++; I tried it with gcc (full program > attached) and it works fine. What errors are you seeing? This program gives me a core dump, because __fg_snd_[0].fn == NULL. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CC compiler problem?
Andy Ross wrote: > Erik Hofman wrote: > > I have a propblem with a peace of CC code which is pretty standard for > > common C. When I define a structure and point an array to a > > pre-defined array; > > > > [...] > > > > this works for C but not for CC? Am I doing something wrong here, or > > doesn't CC allow this type of declaration (and if not, is there an > > alternative)? > > This is perfectly legal C++; I tried it with gcc (full program > attached) and it works fine. What errors are you seeing? the C++ code gives the warning message: fn = NULL while the C code calls log10() twice. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Metakit
Danie Heath wrote: > I'm extremely eager to start developing, but I can't because metakit > won't compile on my Linux system. This is flatly incorrect. Metakit builds just fine on your Linux system. Hey, if you don't provide any documentation for your problems, then I won't document my solutions. :) Seriously: distribution? compiler? metakit version? compilation strategy? error message? Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Comms
Dave Luff wrote: > So supposing a pilot is communicating with approach on comm1, but has > comm2 monitoring the tower, what happens if a stronger tower > transmission is received at the same time as an approach transmission? It doesn't have anything to do with signal strength. The two radios receive the signals independently and provide a plain analog audio output to the panel, which is essentially a mixer. > Will the audio panel loose it, or play them in sequence? It certainly won't play them in sequence -- this is analog electronics we're talking about here. :) In the one installation I've seen, they simply get mixed together and played simultaneously. > And would a pilot actually set his radios up like that, or simply > have the tower frequency in comm1 standby ready to switch over? It's quite common with the folks I've flown with to have ATC on one channel while listening to ATIS on another. As for switching between frequencies under ATC control, my guess is that most people simply use the standby toggle. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com "Men go crazy in conflagrations. They only get better one by one." - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] CC compiler problem?
Erik Hofman wrote:
> I have a propblem with a peace of CC code which is pretty standard for
> common C. When I define a structure and point an array to a
> pre-defined array;
>
> [...]
>
> this works for C but not for CC? Am I doing something wrong here, or
> doesn't CC allow this type of declaration (and if not, is there an
> alternative)?
This is perfectly legal C++; I tried it with gcc (full program
attached) and it works fine. What errors are you seeing?
Andy
--
Andrew J. RossNextBus Information Systems
Senior Software Engineer Emeryville, CA
[EMAIL PROTECTED] http://www.nextbus.com
"Men go crazy in conflagrations. They only get better one by one."
- Sting (misquoted)
#include
#include
double _fg_lin(double arg) { return 0; }
double _fg_log10(double arg) { return 1; }
struct {
string name;
double (*fn)(double);
} __fg_snd_[] =
{
{"lin", _fg_lin},
{"log", _fg_log10},
{"", NULL}
};
int main()
{
cout << (*__fg_snd_[0].fn)(1) << endl;
}
Re: [Flightgear-devel] Comms
> So supposing a pilot is communicating with approach on comm1,
> but has comm2 monitoring the tower, what happens if a stronger
> tower transmission is received at the same time as an approach
> transmission? Will the audio panel loose it, or play them in
> sequence? And would a pilot actually set his radios up like that, or
> simply have the tower frequency in comm1 standby ready to switch
> over?
Nonono; the radios are independent all the way through to the audio that
could feed directly into the speakers so signal strength is irrelevant.
The panel will play all selected inputs over the top of each other.
The current FGFS behavior with the NAV1/2 and ADF idents is a good example.
If IFR on an NDB approach, you are required to monitor the ADF receiver
continuously while using it for navigation. Thus, you are listening to
the morse beeping ("MY" for DEORO for example) while also talking to the
approach controller and (afterwards) to the tower people. Irritating.
You almost never listen to two controllers at once, operationally, because
IFR you are always under the control of exactly one sector/position.
Transitioning from approach to tower is a handoff like any other handoff.
However, when it's quiet, I might listen to the next sector along to get
some idea what it's like up ahead. ... and other similar situations.
When VFR, life is a lot more complicated and I often have two towers on.
Some of the more modern panels allow you to specify that certain input
channels are non-operational, i.e. should be suppressed whenever the pilot
speaks or one of the operational input sources (such as the radios) makes
a noise. Back seat passengers and the CD player are usually good choices.
IFR, I normally have COM1 on approach/center and COM2 on tower/atis/fss.
On aircraft with flipflop, the other side of COM1 is the last frequency
(unless I know we're about to cross a boundary and I know the next freq)
and the other side of COM2 is the unselected one of the tower/atis pair.
I usually use the radio 1/2 select to choose which I'm talking and listening
to, so they don't talk at the same time which is difficult to listen to.
However, any time I hit the "both" button or press the COM1 and COM2 buttons
(depending on panel design), I can potentially hear two controllers talking
at the same time. If the volume is about equal and their voices are
distinctive, it is just like being in a room with two people talking at once.
I'm told that some of the advanced panels, that support stereo headsets,
can place COM1 in the left stereo position and COM2 in the right position.
This makes it much much easier to listen to the two sources at the same time.
For example, when over Lake Hodges at 4k' enroute KCRQ to KMYF, I'm about
to get switched from 127.3 to 132.2 so the former is COM1 active and the latter
is COM1 standby. I know that the next sector's controller is going to have
to read the atis for KMYF to me (unless I've already picked it up).
So, I'll put 126.9 into COM2 with the volume down and listen to both;
when the controller isn't talking, I can hear the atis and (after a few
repeats) I can get the information copied down onto paper. On average,
the 127.3 channel is in use about half the time, and if those transmissions
happen to line up with the same bit of the atis repeat, you can end up
listening to rest of the atis repeat a large number of times. However, if
the two voices are distinctively different, you can pick up the atis content
while still being able to listen and understand the controller. When done,
I take the radio off the both setting, tune 119.2 into COM2 standby and
hit the toggle to put it into COM2's active because I'll need it in 15 min.
When I get the handoff, I just hit COM1's toggle and listen to see whether
the frequency is clear then announce something like ...
SoCal Approach, Cessna 6291R level 4 thousand heading 1 0 0
with information charlie at montgomery
PS ... airline purists will point out that I've got excess words in that,
which is true but irrelevant (since the FAA recommends it) since I'm doing
this on initial contact to confirm the control instruction that I'm subject
to. Unlike airlines that follow fairly rigid routes and STARs, I can end
up doing unusual things and prefer the controllers to have no assumptions.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
> That looks really ugly ... could it be bugs/problems with the sun > linker? Usually the sun assembler and linker - both in /usr/ccs/bin/ - are quite fine with GCC. I've compiled more than 200 OpenSource packages using these tools, so I believe you have to look somwhere else for this bug. After having a short look at the topic I have the impression that some libraries might be missing at the linker command. On Solaris you will need "-lsocket -lnsl" for binaries that do networking. Is this for Sparc or x86 ? I might have missed the message Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
Perhaps gcc-2.95.3 for solaris is generating output that the solaris ld can't understand? Curt. Salman Sheikh writes: > Yes, all were built with gcc version 2.95.3. > > Salman > > > > On Wed, 6 Mar 2002 09:29:10 -0600 (CST) > "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: > > > That looks really ugly ... could it be bugs/problems with the sun > > linker? Have you tried building simple C++ programs with this same > > version of gcc? Did you biuld plib, simgear, flightgear, etc. all > > with the same compiler? > > > > Curt. > > > > > > Salman Sheikh writes: > > > Got that fixed. Now on file linking I get the following error: > > > > > > > > > c++ -DPKGLIBDIR=\"/folks/salman/bin/lib/FlightGear\" -g -O2 >-L/folks/salman/bin/lib -o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o >fgfs.o globals.o options.o splash.o viewer.o viewer_lookat.o viewer_rph.o viewmgr.o >../../src/Aircraft/libAircraft.a ../../src/ATC/libATC.a >../../src/Autopilot/libAutopilot.a ../../src/Cockpit/libCockpit.a >../../src/Controls/libControls.a../../src/FDM/libFlight.a >../../src/FDM/Balloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a >../../src/FDM/YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a >../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a >../../src/GUI/libGUI.a ../../src/Navaids/libNavaids.a >../../src/Scenery/libScenery.a ../../src/Sound/libSound.a >../../src/Airports/libAirports.a ../../src/Network/libNetwork.a >../../src/Objects/libObjects.a ../../src/Time/libTime.a >../../src/WeatherCM/libWeatherCM.a ../../src/Input/libInput.a -lsgroute >-lsgsky -lsgephem -lsg! ti! > mi! > > ng! > > > -lsgio -lsgscreen-lsgmath -lsgbucket -lsgdebug -lsgmagvar -lsgmisc >-lsgxml -lsgserial -lplibpu -lplibfnt -lplibnet -lplibssg -lplibsg >-lmk4 -lz -L/space1/glut-3.7/lib/glut -lglut -lGLU -lGL -lXmu -lXt -lSM >-lICE -lXi -lXext -lX11 -lsocket -lpthread -lm -lplibul -lm > > > ld: warning: relocation error: R_SPARC_32: file >../../src/Cockpit/libCockpit.a(hud_card.o): symbol .LLC238: > > > external symbolic relocation against non-allocatable section .stab; > > > cannot be processed at runtime: relocation ignored > > > ld: warning: relocation error: R_SPARC_32: file >../../src/FDM/libFlight.a(LaRCsimIC.o): symbol .LLC155: > > > external symbolic relocation against non-allocatable section .stab; > > > cannot be processed at runtime: relocation ignored > > > Undefined first referenced > > > symbol in file > > > slScheduler::playSample(slSample *, int, slPreemptMode, int, void (*)(slSample >*, slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > > > slScheduler::~slScheduler(void) ../../src/Sound/libSound.a(soundmgr.o) > > > slDSP::open(char *, int, int, int) ../../src/Sound/libSound.a(soundmgr.o) > > > gethostbyname >../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > > smMixer::smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > > > slDSP::close(void) ../../src/Sound/libSound.a(soundmgr.o) > > > slScheduler::loopSample(slSample *, int, slPreemptMode, int, void (*)(slSample >*, slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > > > __slPendingError../../src/Sound/libSound.a(soundmgr.o) > > > .LLC155 ../../src/FDM/libFlight.a(LaRCsimIC.o) > > > gethostbyaddr >../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > > slSample::autoMatch(slDSP *)../../src/Sound/libSound.a(soundmgr.o) > > > inet_addr >/folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > > slScheduler::init(void) ../../src/Sound/libSound.a(soundmgr.o) > > > slScheduler::stopSample(slSample *, int)../../src/Sound/libSound.a(soundmgr.o) > > > .LLC238 ../../src/Cockpit/libCockpit.a(hud_card.o) > > > inet_ntoa >/folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > > smMixer::~smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > > > slScheduler::addSampleEnvelope(slSample *, int, int, slEnvelope *, >slEnvelopeType)../../src/Sound/libSound.a(soundmgr.o) > > > slSample::loadFile(char *) ../../src/Sound/libSound.a(soundmgr.o) > > > slScheduler::realUpdate(int)../../src/Sound/libSound.a(soundmgr.o) > > > ld: fatal: Symbol referencing errors. No output written to fgfs > > > collect2: ld returned 1 exit status > > > make: *** [fgfs] Error 1 > > > > > > > > ___ > Flightgear-devel
Re: [Flightgear-devel] Comms
Alex Perry writes: > Each radio operates independently and will receive whatever is onchannel. > However, usually the radios (and other things that make noises) are > wired through the so-called audio panel that decides which combination > of sounds is sent to the speaker and/or the headset and/or any other > place that sound can be heard. So supposing a pilot is communicating with approach on comm1, but has comm2 monitoring the tower, what happens if a stronger tower transmission is received at the same time as an approach transmission? Will the audio panel loose it, or play them in sequence? And would a pilot actually set his radios up like that, or simply have the tower frequency in comm1 standby ready to switch over? Cheers - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
Yes, all were built with gcc version 2.95.3. Salman On Wed, 6 Mar 2002 09:29:10 -0600 (CST) "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: > That looks really ugly ... could it be bugs/problems with the sun > linker? Have you tried building simple C++ programs with this same > version of gcc? Did you biuld plib, simgear, flightgear, etc. all > with the same compiler? > > Curt. > > > Salman Sheikh writes: > > Got that fixed. Now on file linking I get the following error: > > > > > > c++ -DPKGLIBDIR=\"/folks/salman/bin/lib/FlightGear\" -g -O2 >-L/folks/salman/bin/lib -o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o >fgfs.o globals.o options.o splash.o viewer.o viewer_lookat.o viewer_rph.o viewmgr.o >../../src/Aircraft/libAircraft.a../../src/ATC/libATC.a >../../src/Autopilot/libAutopilot.a ../../src/Cockpit/libCockpit.a >../../src/Controls/libControls.a../../src/FDM/libFlight.a >../../src/FDM/Balloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a >../../src/FDM/YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a >../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a >../../src/GUI/libGUI.a ../../src/Navaids/libNavaids.a >../../src/Scenery/libScenery.a ../../src/Sound/libSound.a >../../src/Airports/libAirports.a ../../src/Network/libNetwork.a >../../src/Objects/libObjects.a ../../src/Time/libTime.a >../../src/WeatherCM/libWeatherCM.a ../../src/Input/libInput.a -lsgroute >-lsgsky -lsgephem -lsgti! mi! > ng! > > -lsgio -lsgscreen -lsgmath -lsgbucket -lsgdebug -lsgmagvar -lsgmisc -lsgxml > -lsgserial -lplibpu -lplibfnt -lplibnet -lplibssg -lplibsg >-lmk4 -lz -L/space1/glut-3.7/lib/glut -lglut -lGLU -lGL -lXmu -lXt -lSM -lICE >-lXi -lXext -lX11 -lsocket -lpthread -lm -lplibul -lm > > ld: warning: relocation error: R_SPARC_32: file >../../src/Cockpit/libCockpit.a(hud_card.o): symbol .LLC238: > > external symbolic relocation against non-allocatable section .stab; > > cannot be processed at runtime: relocation ignored > > ld: warning: relocation error: R_SPARC_32: file >../../src/FDM/libFlight.a(LaRCsimIC.o): symbol .LLC155: > > external symbolic relocation against non-allocatable section .stab; > > cannot be processed at runtime: relocation ignored > > Undefined first referenced > > symbol in file > > slScheduler::playSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, >slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::~slScheduler(void) ../../src/Sound/libSound.a(soundmgr.o) > > slDSP::open(char *, int, int, int) ../../src/Sound/libSound.a(soundmgr.o) > > gethostbyname >../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > smMixer::smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > > slDSP::close(void) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::loopSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, >slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > > __slPendingError../../src/Sound/libSound.a(soundmgr.o) > > .LLC155 ../../src/FDM/libFlight.a(LaRCsimIC.o) > > gethostbyaddr >../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > slSample::autoMatch(slDSP *)../../src/Sound/libSound.a(soundmgr.o) > > inet_addr >/folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > slScheduler::init(void) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::stopSample(slSample *, int)../../src/Sound/libSound.a(soundmgr.o) > > .LLC238 ../../src/Cockpit/libCockpit.a(hud_card.o) > > inet_ntoa >/folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit >dependency /usr/lib/libnsl.so.1) > > smMixer::~smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::addSampleEnvelope(slSample *, int, int, slEnvelope *, >slEnvelopeType)../../src/Sound/libSound.a(soundmgr.o) > > slSample::loadFile(char *) ../../src/Sound/libSound.a(soundmgr.o) > > slScheduler::realUpdate(int)../../src/Sound/libSound.a(soundmgr.o) > > ld: fatal: Symbol referencing errors. No output written to fgfs > > collect2: ld returned 1 exit status > > make: *** [fgfs] Error 1 > > > > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Metakit
I'm not RH user, but why you don't try to install metakit from distribution's rpm. In debian it work without problem. -- Martin Dressler e-mail: [EMAIL PROTECTED] http://www.musicabona.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Metakit
> Redhat 7.2 Sorry, can't help you then. I'll refer you to the RH users on the list. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Comms
> A few quick questions to the pilots about comm radios - do you > hear transmissions from both comm1 and comm2 if appropriately > tuned in without having to expicitly switch between them. If so, do > simultaneous transmissions get overlaid and garbled or does it just > play the strongest one. And can I assume that two comm radios > is the most anyone will ever have or do some planes have 3, 4, > more? Each radio operates independently and will receive whatever is onchannel. However, usually the radios (and other things that make noises) are wired through the so-called audio panel that decides which combination of sounds is sent to the speaker and/or the headset and/or any other place that sound can be heard. In a C172, all the headsets are usually wired together, so there is only one switchable entry for headsets. Many panels have a "radio 1/2" switch, that decides which radio gets the microphone. In this situation, instead of "COM1" and "COM2" inputs, you might have "SEL" and "UNSEL" "BOTH" buttons, or a combination of them. On a hypothetical C172, your sources are ... COM1 COM2 NAV1 NAV2 ADF MARKER GPS STALL GEAR The latter two are generally not able to be disconnected from the speaker. Often, the rear seat headsets can be disconnected from the front seat ones. This can increase panel complexity, although no effect on other operations. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] view code. was Virtual Cockpit!
On Wed 6. March 2002 16:09, you wrote: > > That looks good -- a single, configurable view manager would be better > > than a few ad-hoc, hard-coded ones. You'll need to be able to specify > > a few more parameters (i.e. draw the 3D model, look towards the plane, > > reverse view direction [for external], etc.). > > So i'm trying to reorganize the code first :-) Hmm, I see that I'm second so I will wait until you finish the changes. Hope you will be succesfull. Regards, Madr -- Martin Dressler e-mail: [EMAIL PROTECTED] http://www.musicabona.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Comms
A few quick questions to the pilots about comm radios - do you hear transmissions from both comm1 and comm2 if appropriately tuned in without having to expicitly switch between them. If so, do simultaneous transmissions get overlaid and garbled or does it just play the strongest one. And can I assume that two comm radios is the most anyone will ever have or do some planes have 3, 4, more? Cheers - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
That looks really ugly ... could it be bugs/problems with the sun linker? Have you tried building simple C++ programs with this same version of gcc? Did you biuld plib, simgear, flightgear, etc. all with the same compiler? Curt. Salman Sheikh writes: > Got that fixed. Now on file linking I get the following error: > > > c++ -DPKGLIBDIR=\"/folks/salman/bin/lib/FlightGear\" -g -O2 -L/folks/salman/bin/lib >-o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o fgfs.o globals.o options.o >splash.o viewer.o viewer_lookat.o viewer_rph.o viewmgr.o >../../src/Aircraft/libAircraft.a ../../src/ATC/libATC.a >../../src/Autopilot/libAutopilot.a ../../src/Cockpit/libCockpit.a >../../src/Controls/libControls.a../../src/FDM/libFlight.a >../../src/FDM/Balloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a >../../src/FDM/YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a >../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a >../../src/GUI/libGUI.a ../../src/Navaids/libNavaids.a >../../src/Scenery/libScenery.a ../../src/Sound/libSound.a >../../src/Airports/libAirports.a ../../src/Network/libNetwork.a >../../src/Objects/libObjects.a ../../src/Time/libTime.a >../../src/WeatherCM/libWeatherCM.a ../../src/Input/libInput.a -lsgroute >-lsgsky -lsgephem -lsgtimi! ng! > -lsgio -lsgscreen-lsgmath -lsgbucket -lsgdebug -lsgmagvar -lsgmisc -lsgxml > -lsgserial -lplibpu -lplibfnt -lplibnet -lplibssg -lplibsg >-lmk4 -lz -L/space1/glut-3.7/lib/glut -lglut -lGLU -lGL -lXmu -lXt -lSM -lICE >-lXi -lXext -lX11 -lsocket -lpthread -lm -lplibul -lm > ld: warning: relocation error: R_SPARC_32: file >../../src/Cockpit/libCockpit.a(hud_card.o): symbol .LLC238: > external symbolic relocation against non-allocatable section .stab; > cannot be processed at runtime: relocation ignored > ld: warning: relocation error: R_SPARC_32: file >../../src/FDM/libFlight.a(LaRCsimIC.o): symbol .LLC155: > external symbolic relocation against non-allocatable section .stab; > cannot be processed at runtime: relocation ignored > Undefined first referenced > symbol in file > slScheduler::playSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, >slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > slScheduler::~slScheduler(void) ../../src/Sound/libSound.a(soundmgr.o) > slDSP::open(char *, int, int, int) ../../src/Sound/libSound.a(soundmgr.o) > gethostbyname ../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) >(symbol belongs to implicit dependency /usr/lib/libnsl.so.1) > smMixer::smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > slDSP::close(void) ../../src/Sound/libSound.a(soundmgr.o) > slScheduler::loopSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, >slEvent, int))../../src/Sound/libSound.a(soundmgr.o) > __slPendingError../../src/Sound/libSound.a(soundmgr.o) > .LLC155 ../../src/FDM/libFlight.a(LaRCsimIC.o) > gethostbyaddr ../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) >(symbol belongs to implicit dependency /usr/lib/libnsl.so.1) > slSample::autoMatch(slDSP *)../../src/Sound/libSound.a(soundmgr.o) > inet_addr /folks/salman/bin/lib/libplibnet.a(netSocket.o) >(symbol belongs to implicit dependency /usr/lib/libnsl.so.1) > slScheduler::init(void) ../../src/Sound/libSound.a(soundmgr.o) > slScheduler::stopSample(slSample *, int)../../src/Sound/libSound.a(soundmgr.o) > .LLC238 ../../src/Cockpit/libCockpit.a(hud_card.o) > inet_ntoa /folks/salman/bin/lib/libplibnet.a(netSocket.o) >(symbol belongs to implicit dependency /usr/lib/libnsl.so.1) > smMixer::~smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) > slScheduler::addSampleEnvelope(slSample *, int, int, slEnvelope *, >slEnvelopeType)../../src/Sound/libSound.a(soundmgr.o) > slSample::loadFile(char *) ../../src/Sound/libSound.a(soundmgr.o) > slScheduler::realUpdate(int)../../src/Sound/libSound.a(soundmgr.o) > ld: fatal: Symbol referencing errors. No output written to fgfs > collect2: ld returned 1 exit status > make: *** [fgfs] Error 1 > > > > > > On Tue, 5 Mar 2002 21:26:48 - > "D Luff" <[EMAIL PROTECTED]> wrote: > > > Salman Sheikh writes: > > > > > Hello All, > > > > > > Got past the first error. Got a new one: > > > > > > Making all in NetworkOLK > > > c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src >-I/folks/salman/bin/include -I/usr/local/include -g -O2 -c net_send.cxx > > > net_send.cxx: In function `void fgd_init()': > > > net_send.cxx:277: `INADDR_NONE' undeclared (first use this function) > > > net_send.cxx:277: (Each undeclared
Re: [Flightgear-devel] view code. was Virtual Cockpit!
> > That looks good -- a single, configurable view manager would be better > than a few ad-hoc, hard-coded ones. You'll need to be able to specify > a few more parameters (i.e. draw the 3D model, look towards the plane, > reverse view direction [for external], etc.). > So i'm trying to reorganize the code first :-) But there are som properties which I fully don't understand pilot for what is this, it drive only if cur_fdm_state is copied to cur_view_fdm, but I don't know any case when isn't used current fdm. 0.00 pilot view 0.00 0.00 0.00 0.00 0.00 0.00 It is offset from CG? But only YASim set this values. 0.00 0.00 What is this ? chase view 180.0 0 25 180.00 0.00 25.00 What about this property system. The last I suggest doesn't allow to easy change via command line options. pilot view 0 0 0.0 0.0 0.0 true what more panel? hud? hear is tree of current values chase view 180.0 0 25 false what more panel? hud? hear is tree of current values Regards, Madr -- Martin Dressler e-mail: [EMAIL PROTECTED] http://www.musicabona.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Solaris compile error
Got that fixed. Now on file linking I get the following error: c++ -DPKGLIBDIR=\"/folks/salman/bin/lib/FlightGear\" -g -O2 -L/folks/salman/bin/lib -o fgfs main.o fg_commands.o fg_init.o fg_io.o fg_props.o fgfs.o globals.o options.o splash.o viewer.o viewer_lookat.o viewer_rph.o viewmgr.o ../../src/Aircraft/libAircraft.a../../src/ATC/libATC.a ../../src/Autopilot/libAutopilot.a ../../src/Cockpit/libCockpit.a ../../src/Controls/libControls.a../../src/FDM/libFlight.a ../../src/FDM/Balloon/libBalloon.a ../../src/FDM/JSBSim/libJSBSim.a ../../src/FDM/YASim/libYASim.a ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a ../../src/FDM/LaRCsim/libLaRCsim.a ../../src/FDM/UIUCModel/libUIUCModel.a ../../src/GUI/libGUI.a ../../src/Navaids/libNavaids.a ../../src/Scenery/libScenery.a ../../src/Sound/libSound.a ../../src/Airports/libAirports.a ../../src/Network/libNetwork.a ../../src/Objects/libObjects.a ../../src/Time/libTime.a../../src/WeatherCM/libWeatherCM.a ../../src/Input/libInput.a -lsgroute -lsgsky -lsgephem -lsgtiming! -lsgio -lsgscreen -lsgmath -lsgbucket -lsgdebug -lsgmagvar -lsgmisc -lsgxml -lsgserial -lplibpu -lplibfnt -lplibnet -lplibssg -lplibsg -lmk4 -lz -L/space1/glut-3.7/lib/glut -lglut -lGLU -lGL -lXmu -lXt -lSM -lICE -lXi -lXext -lX11 -lsocket -lpthread -lm -lplibul -lm ld: warning: relocation error: R_SPARC_32: file ../../src/Cockpit/libCockpit.a(hud_card.o): symbol .LLC238: external symbolic relocation against non-allocatable section .stab; cannot be processed at runtime: relocation ignored ld: warning: relocation error: R_SPARC_32: file ../../src/FDM/libFlight.a(LaRCsimIC.o): symbol .LLC155: external symbolic relocation against non-allocatable section .stab; cannot be processed at runtime: relocation ignored Undefined first referenced symbol in file slScheduler::playSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, slEvent, int))../../src/Sound/libSound.a(soundmgr.o) slScheduler::~slScheduler(void) ../../src/Sound/libSound.a(soundmgr.o) slDSP::open(char *, int, int, int) ../../src/Sound/libSound.a(soundmgr.o) gethostbyname ../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) smMixer::smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) slDSP::close(void) ../../src/Sound/libSound.a(soundmgr.o) slScheduler::loopSample(slSample *, int, slPreemptMode, int, void (*)(slSample *, slEvent, int))../../src/Sound/libSound.a(soundmgr.o) __slPendingError../../src/Sound/libSound.a(soundmgr.o) .LLC155 ../../src/FDM/libFlight.a(LaRCsimIC.o) gethostbyaddr ../../src/FDM/JSBSim/libJSBSim.a(FGfdmSocket.o) (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) slSample::autoMatch(slDSP *)../../src/Sound/libSound.a(soundmgr.o) inet_addr /folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) slScheduler::init(void) ../../src/Sound/libSound.a(soundmgr.o) slScheduler::stopSample(slSample *, int)../../src/Sound/libSound.a(soundmgr.o) .LLC238 ../../src/Cockpit/libCockpit.a(hud_card.o) inet_ntoa /folks/salman/bin/lib/libplibnet.a(netSocket.o) (symbol belongs to implicit dependency /usr/lib/libnsl.so.1) smMixer::~smMixer(void) ../../src/Sound/libSound.a(soundmgr.o) slScheduler::addSampleEnvelope(slSample *, int, int, slEnvelope *, slEnvelopeType)../../src/Sound/libSound.a(soundmgr.o) slSample::loadFile(char *) ../../src/Sound/libSound.a(soundmgr.o) slScheduler::realUpdate(int)../../src/Sound/libSound.a(soundmgr.o) ld: fatal: Symbol referencing errors. No output written to fgfs collect2: ld returned 1 exit status make: *** [fgfs] Error 1 On Tue, 5 Mar 2002 21:26:48 - "D Luff" <[EMAIL PROTECTED]> wrote: > Salman Sheikh writes: > > > Hello All, > > > > Got past the first error. Got a new one: > > > > Making all in NetworkOLK > > c++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src >-I/folks/salman/bin/include -I/usr/local/include -g -O2 -c net_send.cxx > > net_send.cxx: In function `void fgd_init()': > > net_send.cxx:277: `INADDR_NONE' undeclared (first use this function) > > net_send.cxx:277: (Each undeclared identifier is reported only once > > net_send.cxx:277: for each function it appears in.) > > make[1]: *** [net_send.o] Error 1 > > make: *** [all-recursive] Error 1 > > > > > > Any ideas anyone? > > Hi Salman, > > NetworkOLK isn't needed to run the sim, so you can: > > ./configure --with-network-olk=no > > Cheers - Dave > > -- > [EMAIL PROTECTED] > > ___
Re: [Flightgear-devel] Virtual cockpit update
> Which leads me to a random digression: does anyone have a good > reference on historic HUD symbology? Not MIL-STD documents about > current fighters, nor research papers on what would be cool, but > actual photos and descriptions of the HUDs installed on (just for the > sake of argument) the Harriers and late model A-4's. :) > If you want F-15C HUD info, let me know. I can bury you in short order. :) g. -- "I'm not crazy, I'm plausibly off-nominal!" http://www.f15sim.com - The only one of its kind. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] CC compiler problem?
Hi,
I have a propblem with a peace of CC code which is pretty standard for
common C. When I define a structure and point an array to a pre-defined
array;
struct {
string name;
double (*fn)(double);
} __fg_snd_[] =
{
{"lin", _fg_lin},
{"log", _fg_log10},
{"", NULL}
};
this works for C but not for CC?
Am I doing something wrong here, or doesn't CC allow this type of
declaration (and if not, is there an alternative)?
Erik
#include
#include
#include
using std::string;
double _fg_lin(double v) { return v; };
double _fg_log10(double v) { return (v < 1) ? 0 : log10(v+1); };
struct {
string name;
double (*fn)(double);
} __fg_snd_[] =
{
{"lin", _fg_lin},
{"log", _fg_log10},
{"", NULL}
};
int main() {
double (*fn)(double) = NULL;
for (int j=0; __fg_snd_[j].fn; j++) {
printf("j = %i\n", j);
if (__fg_snd_[j].name == "log") {
fn = __fg_snd_[j].fn;
break;
}
}
if (!fn) {
printf("fn = NULL\n");
return -1;
}
printf("fn(0) = %f\n", fn(0));
printf("fn(10) = %f\n", fn(10));
return 0;
}
#include
#include
#include
double _fg_lin(double v) { return v; };
double _fg_log10(double v) { return (v < 1) ? 0 : log10(v+1); };
const struct {
char name[3];
double (*fn)(double);
} __fg_snd_[] =
{
{"lin", _fg_lin},
{"log", _fg_log10},
{"", NULL}
};
int main() {
double (*fn)(double);
int j;
for (j=0; __fg_snd_[j].fn; j++) {
printf("j = %i\n", j);
if (!strncmp(__fg_snd_[j].name, "log", 3)) {
fn = __fg_snd_[j].fn;
break;
}
}
if (!fn) {
printf("fn = NULL\n");
return -1;
}
printf("fn(0) = %f\n", fn(0));
printf("fn(10) = %f\n", fn(10));
return 0;
}
Re: [Flightgear-devel] techtv
Curtis L. Olson wrote: > Looks like we are getting a few techtv visitors to the web site this > evening: > > http://seneca.flightgear.org/webalizer/usage_200203.html You can find the text here: http://www.techtv.com/screensavers/answerstips/story/0,24330,3327281,00.html Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
