Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
On Donnerstag, 8. Juli 2004 02:23, Oliver C. wrote: > My question is now, does it really make sense to create a work around for > this, isn't it better to update the STL library? > IMHO the STL makes sense, it saves space, keeps the code clean, programmers > don't need to invent the wheel a second time and you will need the STL > anyway so why shouldn't we use it? I would like to use the C++ native way to get these informations! And RedHat shipped a long time with that old gcc. But, IMO the sense of software is not to make the sysadmin installing it more work because of the raising requirements ... At least not if the workaround is 5 minutes of work ... Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
On Wednesday 07 July 2004 17:44, Jon S Berndt wrote: > On Wed, 7 Jul 2004 15:30:14 - > > "Jim Wilson" <[EMAIL PROTECTED]> wrote: > >There doesn't seem to be support for the std::numeric_limits > >references added > >in the June update. Can we work around this? > > > >e.g.: > > > >In file included from FGFCSComponent.h:46, > > from FGDeadBand.h:40, > > from FGDeadBand.cpp:40: > >./FGJSBBase.h:41:18: limits: No such file or directory > > > >>From FGJSBBase.h: > > > >#include > > Looks like Mathias added this. It looks like it compiles under CygWin. > It's present under IRIX, and it's also present under whatever Linux > Mathias is using. Strange. In any case, the #include > statement needs to be put in the correct #ifdef block, similar to the > rest of the c++ headers. I had the same problem on Slackware 8.1. The problem was, that the STL library on Slackware 8.1 was too old. Updating the STL library should solve the problem. The easiest way to do this is off course by updating the distribution. ;) My question is now, does it really make sense to create a work around for this, isn't it better to update the STL library? IMHO the STL makes sense, it saves space, keeps the code clean, programmers don't need to invent the wheel a second time and you will need the STL anyway so why shouldn't we use it? Best Regards, Oliver C. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
Jim Wilson wrote: > Jon S Berndt said: > > > On Wed, 7 Jul 2004 17:35:31 - > > "Jim Wilson" <[EMAIL PROTECTED]> wrote: > > >Mathias Fröhlich said: > > > > > >> On Mittwoch, 7. Juli 2004 17:30, Jim Wilson wrote: > > >> > There doesn't seem to be support for the std::numeric_limits > > >>references > > >> > added in the June update. Can we work around this? > > >> Done in JSBSim's cvs. > > >> > > >> Please check out a new version. > > >> > > > > > >I don't see anything in JSBSim CVS that addresses this problem. Did > > >you read the later posts? > > > > Jim: > > > > If you are browsing CVS, there is a lag between what is committed and > > what is presented, I think. If you downloaded from CVS and there is > > still a problem, that would be surprising - CVS is "immediate." Are > > you still seeing the offending code? > > That would explain the problem. I'm using the browser. Currently no changes > show. CVS on SourceForge isn't immediate for anonymous access. Only people that connect through ssh see the real repository. Others are seeing the backup server that is updated several times a day. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
Jon S Berndt said: > On Wed, 7 Jul 2004 17:35:31 - > "Jim Wilson" <[EMAIL PROTECTED]> wrote: > >Mathias Fröhlich said: > > > >> On Mittwoch, 7. Juli 2004 17:30, Jim Wilson wrote: > >> > There doesn't seem to be support for the std::numeric_limits > >>references > >> > added in the June update. Can we work around this? > >> Done in JSBSim's cvs. > >> > >> Please check out a new version. > >> > > > >I don't see anything in JSBSim CVS that addresses this problem. Did > >you read the later posts? > > Jim: > > If you are browsing CVS, there is a lag between what is committed and > what is presented, I think. If you downloaded from CVS and there is > still a problem, that would be surprising - CVS is "immediate." Are > you still seeing the offending code? That would explain the problem. I'm using the browser. Currently no changes show. Thanks, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
On Wed, 7 Jul 2004 17:35:31 - "Jim Wilson" <[EMAIL PROTECTED]> wrote: Mathias Fröhlich said: On Mittwoch, 7. Juli 2004 17:30, Jim Wilson wrote: > There doesn't seem to be support for the std::numeric_limits references > added in the June update. Can we work around this? Done in JSBSim's cvs. Please check out a new version. I don't see anything in JSBSim CVS that addresses this problem. Did you read the later posts? Jim: If you are browsing CVS, there is a lag between what is committed and what is presented, I think. If you downloaded from CVS and there is still a problem, that would be surprising - CVS is "immediate." Are you still seeing the offending code? Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
Mathias Fröhlich said: > On Mittwoch, 7. Juli 2004 17:30, Jim Wilson wrote: > > There doesn't seem to be support for the std::numeric_limits references > > added in the June update. Can we work around this? > Done in JSBSim's cvs. > > Please check out a new version. > I don't see anything in JSBSim CVS that addresses this problem. Did you read the later posts? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
On Mittwoch, 7. Juli 2004 17:30, Jim Wilson wrote: > There doesn't seem to be support for the std::numeric_limits references > added in the June update. Can we work around this? Done in JSBSim's cvs. Please check out a new version. Greetings Mathias -- Mathias FrÃhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
Jon S Berndt said:
> On Wed, 7 Jul 2004 15:30:14 -
> "Jim Wilson" <[EMAIL PROTECTED]> wrote:
> >There doesn't seem to be support for the std::numeric_limits
> >references added
> >in the June update. Can we work around this?
> >
> >e.g.:
> >
> >In file included from FGFCSComponent.h:46,
> > from FGDeadBand.h:40,
> > from FGDeadBand.cpp:40:
> >./FGJSBBase.h:41:18: limits: No such file or directory
> >
> >>From FGJSBBase.h:
> >
> >#include
>
> Looks like Mathias added this. It looks like it compiles under CygWin.
> It's present under IRIX, and it's also present under whatever Linux
> Mathias is using. Strange. In any case, the #include
> statement needs to be put in the correct #ifdef block, similar to the
> rest of the c++ headers.
>
In FGKinemat.cpp,
Would
while ( 0.0 < dt && fabs(Input - Output) < 0.1) {
work for this rather than:
while ( 0.0 < dt && !EqualToRoundoff(Input, Output) ) {
???
Sometimes the simplist solutions are best. I would think that in many cases
integrating variations in precision on different platforms would not always be
a good thing to do.
The above line of code is the only place the limits and the EqualtToRoundoff
functions built with them, are referenced.
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim compile failing on Redhat 7.3
On Wed, 7 Jul 2004 15:30:14 - "Jim Wilson" <[EMAIL PROTECTED]> wrote: There doesn't seem to be support for the std::numeric_limits references added in the June update. Can we work around this? e.g.: In file included from FGFCSComponent.h:46, from FGDeadBand.h:40, from FGDeadBand.cpp:40: ./FGJSBBase.h:41:18: limits: No such file or directory From FGJSBBase.h: #include Looks like Mathias added this. It looks like it compiles under CygWin. It's present under IRIX, and it's also present under whatever Linux Mathias is using. Strange. In any case, the #include statement needs to be put in the correct #ifdef block, similar to the rest of the c++ headers. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
