Re: [Flightgear-devel] Re: ld: Undefined symbols error linking fgfs 0.9.1
Quoth Andy Ross: Some of the missing symbols (slScheduler et. al.) should be found in the Plib sl library, which for some reason doesn't appear on your linker command line. The reason is that $HOSTTYPE is not macintosh, it is powerpc. I checked 10.0.4 and 10.1 on a TiBook, and 10.2 on a G4 tower, and uname -p reports powerpc in all three instances. So I don't know where the original value macintosh came from. There are three instances of '$HOSTTYPE = macintosh' in configure that need to be changed to powerpc. See below. I am getting to the final link again, but getting a much different error. Progress! # less configure [...] # Check for audio support echo $as_me:$LINENO: checking for audio support 5 echo $ECHO_N checking for audio support... $ECHO_C 6 audio_LIBS= if test -r /usr/include/soundcard.h \ -o -r /usr/include/linux/soundcard.h \ -o -r /usr/include/machine/soundcard.h \ -o -r /usr/include/audio.h \ -o x$ac_cv_header_windows_h = xyes \ -o $HOSTTYPE = macintosh; then cat confdefs.h \_ACEOF #define ENABLE_AUDIO_SUPPORT 1 _ACEOF audio_LIBS=-lplibsl -lplibsm [...] # ./configure [...] checking for audio support... no [...] Regards, David K. Drum [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: ld: Undefined symbols error linking fgfs 0.9.1
Your best bet is to check the detailed results in config.log when configure failes a check which you think ought to pass. Regards, Curt. David Drum writes: I am getting to the final link again, but getting a much different error. Progress! # less configure [...] # Check for audio support echo $as_me:$LINENO: checking for audio support 5 echo $ECHO_N checking for audio support... $ECHO_C 6 audio_LIBS= if test -r /usr/include/soundcard.h \ -o -r /usr/include/linux/soundcard.h \ -o -r /usr/include/machine/soundcard.h \ -o -r /usr/include/audio.h \ -o x$ac_cv_header_windows_h = xyes \ -o $HOSTTYPE = macintosh; then cat confdefs.h \_ACEOF #define ENABLE_AUDIO_SUPPORT 1 _ACEOF audio_LIBS=-lplibsl -lplibsm [...] # ./configure [...] checking for audio support... no [...] Regards, David K. Drum [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- 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] Re: ld: Undefined symbols error linking fgfs 0.9.1
James Turner writes:
BTW, I haven't even got as far as linking due to problems with PLIB CVS
versions (Mac gcc keeps moaning about Plib's ul.h, it seems to be
getting included as C file, not a C++ one, and hence function
overloading is not permitted). Haven't taken this up with the plib guys
yet.
I seem to recall someone saying that anything installed in
/usr/include on a Mac get's automatically wrapped with something like:
extern C { }
This is annoying because plib automatically installs in /usr/lib (even
though it really shouldn't.) :-)
The trick is to override the install location at configure time with
something like:
./configure --prefix=/usr/local
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] Re: ld: Undefined symbols error linking fgfs 0.9.1
On Sunday, December 8, 2002, at 04:15 am, Andy Ross wrote: David Drum wrote: I am compiling FG 0.9.1 on Mac OS X. ld: Undefined symbols: _CPSEnableForegroundOperation _CPSGetCurrentProcess _CPSSetFrontProcess _CPSSetProcessName [...] I sent this to flightgear-users a couple days ago when 0.9.0 was out. No response. My word. The reason these symbols are undefined is they're undocumented 'secret' Apple APIs (but very useful ones). They are used to assemble a hack that is doing the rounds of many ported Unix tools and libs : for example libSDL and gtk-quartz. I have so far contacted two people trying to trace the origins of the hack (waiting for Max Horn at the Fink project to see if he can find his source). I am probably going to propose this hack as an addition to debug builds of Mozilla (MachO builds), so it's getting fairly widespread : I didn't realize it has made it into FG / plib though. Anyway, you need to link against an extra library. I did this: grep -r CPSEnableForegroundOperation /System, and got the following (on Jaguar, be warned the link library may be different on Puma) And it seems that the symbols are in the CoreGraphics framework (which you should get as part of CoreServices). I assume that for FG and plib we only link against Carbon, so of course we don't pick up any 'extra' CoreServices functions like this. BTW, doing this: nm /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ CoreGraphics.framework/CoreGraphics | grep CPS turned up a whole slew of interestingly named methods! :-) BTW, I haven't even got as far as linking due to problems with PLIB CVS versions (Mac gcc keeps moaning about Plib's ul.h, it seems to be getting included as C file, not a C++ one, and hence function overloading is not permitted). Haven't taken this up with the plib guys yet. HH James -- There is no such thing as a humble opinion. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: ld: Undefined symbols error linking fgfs 0.9.1
On Sun, 8 Dec 2002 15:31:42 -0600, Curtis L. Olson [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]: Arnt Karlsen writes: ..should'nt this be the normal default place to drop FG etc cvs and tarballed code, allowing deb and rpm packagers to put their stuff in /usr? The rpmdb does not know about stuff dropped in outside rpm, I suspect deb works the same way. ... not according to the plib developers, they have no concern for package management I guess ... ..maybe roll our own ./configure --prefix=/usr/local'ed plib? Curt. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
