-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks to timoore on IRC for helping find the cause of this.
It seems that a recent checkin broke the build system if osg is installed in a
custom location.
- --with-osg=/home/anmaster/local/flightgear-osg in my case.
I got this from configure:
I just committed a patch that should fix this configure.ac problem. Guys,
it looks like no one tested this patch before committing it, or didn't look
close enough at the result. It doesn't bother me that mistakes happen once
in a while ... this is the dev tree after all, but it makes me nervous
Curtis Olson wrote:
I just committed a patch that should fix this configure.ac problem.
Guys, it looks like no one tested this patch before committing it
It worked for me. Probably because my LD_LIBRARY_PATH is set such
that the resulting configure-generated programs can run?
The genesis of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Curtis Olson wrote:
Are you building on the Mac OSX platform?
No. On Gentoo Linux (x86_64)
Regards,
Arvid Norlander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)
Are you building on the Mac OSX platform?
Curt.
On Jan 11, 2008 4:18 AM, AnMaster wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thanks to timoore on IRC for helping find the cause of this.
It seems that a recent checkin broke the build system if osg is installed
in a custom
Hi all,
I've been experiencing some more weird behaviour from pid
controllers and filters.
I had a pid controller that was working ok (but had some room for
further fine-tuning) but after amending the config and re-loading
the autopilot it seemed to be working randomly. I reverted back to
Hmmm, ok the author of the most recent patch misunderstands the use of the
AM_CONDITIONAL() This does not produce a value that can later be used in
the configure script. Instead it ties into the Makefile.am and can activate
one set of rules or another.
I'll take a look to see if I can unwind
On Jan 11, 2008 10:57 AM, Andy Ross [EMAIL PROTECTED] wrote:
It worked for me. Probably because my LD_LIBRARY_PATH is set such
that the resulting configure-generated programs can run?
The genesis of the commit was a complaint on the IRC channel by Hans
that the OS X build had been broken
On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
On Friday 11 January 2008, LeeE wrote:
I've had a look at the relevant code but as I'm not up on c++ I'm
not sure about what I'm looking at but at lines 798-802 there's:
void FGXMLAutopilot::reinit() {
components.clear();
On Friday 11 January 2008, Curtis Olson wrote:
On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
Try commenting out the call to build() from the code that you quoted
above.
build() is called inside init(), so there should be no need to call it
again
after init().
I suspect the build()
On Friday 11 January 2008 21:50, Curtis Olson wrote:
On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
On Friday 11 January 2008, LeeE wrote:
I've had a look at the relevant code but as I'm not up on c++
I'm not sure about what I'm looking at but at lines 798-802
there's:
void
On Friday 11 January 2008 23:49, LeeE wrote:
On Friday 11 January 2008 21:50, Curtis Olson wrote:
On Jan 11, 2008 3:14 PM, Roy Vegard Ovesen wrote:
On Friday 11 January 2008, LeeE wrote:
I've had a look at the relevant code but as I'm not up on
c++ I'm not sure about what I'm looking
tower:ch53e$ gdb fgfs --aircraft=ch53e --timeofday=noon
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY,
Josh Babcock wrote:
tower:ch53e$ gdb fgfs --aircraft=ch53e --timeofday=noon
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
14 matches
Mail list logo