On Sat, 2010-07-24 at 08:15 -0700, cas...@mminternet.com wrote:
> Having some problems with a new 2.0 build for FG starting with SimGear..
> (files downloaded from git server)
>
> Version FG-1.9.1 ran with boost from a staged library and that worked;
> with the latest that failed so first did a boost build that was successful
> as in ...
Hi John W,
Just for information I sent the attached patch
to 'Thomas' to 'fix' the AX_BOOST_BASE macro
in our acinclude.m4 to account for using the 'stage'
(uninstalled) version of boost around July 13,
but have had no response yet... maybe my email
went astray ???
This patch is against the latest version of this
macro at :-
http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_boost_base.m4
so you have to update our older SG acinclude.m4 to
this first before applying this patch... note the
#serial 13
line, which I changed to 14, must go before all other
lines in acinclude.m4...
As Torsten points out, yes, you need to be using
--with-boost=<dir>, but assume you were doing this, and
although SG only needs the 'headers', you will
note this general macro _DOES_ check for a <dir>/lib
directory, before adjusting the BOOST_CPPFLAGS ;=((
Maybe we could adopt this change, even if the
git AX_BOOST_BASE macro does not get changed/fixed. And
then we could also consider dropping the check for the
'lib' directory... until such time as we do start
needing the libraries...
Hope this helps.
Regards,
Geoff.
attached: bb-14.2.patch
PS: A copy of the full text of what I wrote to
Thomas is at :-
http://geoffair.net/tmp/boost-01.txt
--- ax_boost_base.m4 2010-07-12 18:13:56.000000000 +0200
+++ ax_boost_base-14.2.m4 2010-07-12 20:08:16.000000000 +0200
@@ -33,7 +33,7 @@
# and this notice are preserved. This file is offered as-is, without any
# warranty.
-#serial 13
+#serial 14
AC_DEFUN([AX_BOOST_BASE],
[
@@ -155,6 +155,12 @@
BOOST_CPPFLAGS="-I$ac_boost_path/include/boost-$VERSION_UNDERSCORE"
done
fi
+ if test "$_version" = "0" && test -d "$ac_boost_path" && test -r "$ac_boost_path"; then
+ if test -f $ac_boost_path/boost/version.hpp && test -d $ac_boost_path/stage/lib; then
+ BOOST_LDFLAGS="-L$ac_boost_path/stage/lib"
+ BOOST_CPPFLAGS="-I$ac_boost_path"
+ fi
+ fi
else
if test "$cross_compiling" != yes; then
for ac_boost_path in /usr /usr/local /opt /opt/local ; do
@@ -189,6 +195,13 @@
BOOST_CPPFLAGS="-I$BOOST_ROOT"
BOOST_LDFLAGS="-L$BOOST_ROOT/stage/$libsubdir"
fi
+ else
+ if test -d "$BOOST_ROOT" && test -r "$BOOST_ROOT" && test -d "$BOOST_ROOT/stage/lib" && test -r "$BOOST_ROOT/stage/lib"; then
+ # AC_MSG_NOTICE(We will use a staged boost library from $BOOST_ROOT) # this breaks the nice 'yes' lining
+ BOOST_CPPFLAGS="-I$BOOST_ROOT"
+ BOOST_LDFLAGS="-L$BOOST_ROOT/stage/lib"
+ ac_boost_path="$BOOST_ROOT"
+ fi
fi
fi
fi
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
