Re: [FR-main] Building FreeRaider problem

[Steven W. <swi...@so...>]

I suspected this., ust wanted to check before taking extreme measures.  I=
've=20
tried forcing BitSet to use the non-asm code and had the same results. Th=
e=20
problem appears to be related with the float2long() being included. I did=
 a=20
quick test of adding an AddFloat() method to frnetbit that handles the fu=
ll=20
conversion and the problem goes away.

Is the bit codec going to replace this low level calling? If so, that wil=
l=20
remove my problem long term ... I'm not ready yet to upgrade GCC or Linux.

On Sunday 26 May 2002 03:18, Norman Kr=E4mer wrote:
> The only real solution to this is to use a less buggy compiler :(
> We ran into similar problems in CrystalSpace already. While one could a=
rgue
> thats its possible to rearrange the code to make the compiler happy the
> fact that the compiler does not spill out warnings but _segfaults_ rend=
ers
> any code rearrangements futile.
> GCC 2.95.2 and 2.95.3 are both working. Maybe 3.1 does too.
>
> greetings
> norman
>
> p.s.:
> I think the cause is the use of assembler instructions in the underlyin=
g CS
> source in CS/include/csutil/bitset.h
>
> On Sunday 26 May 2002 04:49, Steven Wilcoxon wrote:
> > I've decided to build FreeRaider to get a better idea of its current
> > condition and am running into a compile problem.

<SNIP>
> > ------------------------------
> > If I comment out all references to AddBits, its willing to compile bu=
t
> > fails with a similar problem in the next module.
> >
> > Has this issue been seen before? Is there a work around?
> >
> > S.W.
> > aka Learner
> > http://www.Terminuspoint.com

<SNIP>
> > _______________________________________________
> > Freeraider-main mailing list
> > Fre...@li...
> > https://lists.sourceforge.net/lists/listinfo/freeraider-main

--=20
S.W.
aka Learner
http://www.TerminusPoint.com