Here's another way of getting the job done.
This is tidier in the sense that it leaves simgear unchanged.
commit cd0af70c868210f46584a1e5e922364b9f2e63ce
Author: John Denker
Date: Mon Dec 14 11:50:53 2009 -0700
Print SIMGEAR_VERSION as a string, even though it doesn't come with quote
mar
On 12/14/2009 11:08 AM, Csaba Halász wrote:
> It is used in the *flightgear* configure.ac script. FG can't find
> simgear anymore because it can't parse the version. Easy to fix there
> but maybe other projects (such as terragear or fgrun) also depend on
> it.
A fully-compatible fix is attached b
> It's a NaN! Sorry :)
So now we know where all these NaN errors have been coming from! ;-)
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_
On Mon, Dec 14, 2009 at 6:54 PM, John Denker wrote:
>
> I tested it. It works fine chez moi.
> make clean ; ./configure --lots-of-options ; make
>
> Can somebody say in more detail what the problem is?
> I can't even find anywhere it is used within simgear.
It is used in the *flightgear* configu
On 12/14/2009 10:30 AM, Erik Hofman wrote:
> Csaba Halász wrote:
>> The recent change which makes a string from the simgear version breaks
>> FG configure.
>> I don't think introducing an incompatible change to the version macro
>> is a good idea.
>> Erik, can you explain why you made the change? I
Csaba Halász wrote:
> The recent change which makes a string from the simgear version breaks
> FG configure.
> I don't think introducing an incompatible change to the version macro
> is a good idea.
> Erik, can you explain why you made the change? I am aware that FG's
> own version is a string, so
The recent change which makes a string from the simgear version breaks
FG configure.
I don't think introducing an incompatible change to the version macro
is a good idea.
Erik, can you explain why you made the change? I am aware that FG's
own version is a string, so I am guessing that might have be
7 matches
Mail list logo
