I've found on some pseudo-POSIX Windows systems that the build only
finds PLIB when you specify --plib-prefix=/usr/. Weird, but that can be
what it takes; and it may be similar on OS X.

The other tactic is to specify --prefix=/fg or some other value for
every compile; PLIB, SimGear, FGFS.

My 2 cents.

Giles Robertson

-----Original Message-----
From: Curtis L. Olson [mailto:[EMAIL PROTECTED] 
Sent: 10 November 2004 18:59
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X

Arthur Wiebe wrote:

>Hello. I think I have plib built and installed. Using GCC 3.3 and PLIB
>straight from CVS 2004-11-08.
>
>Looking in /usr/include/plib and /usr/lib/ it looks like plib is
installed.
>
>The only problem I now have is when trying to configure simgear from
>CVS (same date) I get:
>
>checking plib/ul.h usability... no
>checking plib/ul.h presence... yes
>configure: WARNING: plib/ul.h: present but cannot be compiled
>configure: WARNING: plib/ul.h:     check for missing prerequisite
headers?
>configure: WARNING: plib/ul.h: see the Autoconf documentation
>configure: WARNING: plib/ul.h:     section "Present But Cannot Be
Compiled"
>configure: WARNING: plib/ul.h: proceeding with the preprocessor's
result
>configure: WARNING: plib/ul.h: in the future, the compiler will take
precedence
>configure: WARNING:     ## ------------------------------------------
##
>configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.
##
>configure: WARNING:     ## ------------------------------------------
##
>checking for plib/ul.h... yes
>checking for plib 1.6.0 or newer... wrong version
>configure: error: Install plib 1.6.0 or later first...
>
>That has to mean something.
>
>I tried changing the version in ul.h but that didn't help :). Could
>you send me your compiled files (from /usr/lib/libplibXXX and
>/usr/include/plib) and see if if that works? I would love to make an
>installer package for Mac OS X which would install plib for other OSX
>users without having to compile it.
>  
>

The details of the configure script failure can be found in the 
config.log file.  That may shed some light on exactly what is going
wrong.

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-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

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

Reply via email to