[Oslib-devel] Re: oslib

[Luca A. <luc...@em...>]

Hi Ben,

> Hi, i'm trying to compile oslib on linux, unfortunatly i'm getting the 
> following error
> 
> ../ll/i386/mem.h: In function 'memscan':
> ../ll/i386/mem.h:308: error: parse error before "repnz"
> ../ll/i386/mem.h:309: error: 'scasb' undeclared(first use of function)
> ../ll/i386/mem.h:309: error: (Each undeclated identifier is reported only 
> once
> ../ll/i386/mem.h:309: error: for each function it appears in.)
> ../ll/i386/mem.h:309:21: invalid suffix "f" on integet constant
> ../ll/i386/mem.h:311:17: missing terminating " character
I assume you are using the "January 31st" snapshot? Try the cvs head
(see http://oslib.sourceforge.net/cvs.html), it has fixes for the asm()
stuff.

> i'm using gcc version 3.3.2.
Here, I have gcc 3.2:
[luca@passo oslib]$ gcc -v
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.2/specs
Configured with: ../configure --prefix=/usr --libdir=/usr/lib
--with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix --disable-checking
--enable-long-long --enable-__cxa_atexit
--enable-languages=c,c++,ada,f77,objc,java
--host=i586-mandrake-linux-gnu --with-system-zlib
Thread model: posix
gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk)

The snapshot gives warnings, but no fatal errors... Maybe in gcc 3.3
such 3.2 warning became an error.

I never tried to compile with gcc 3.3... The cvs head should compile
fine, but I am not sure. Let me know.

				Luca
P.S.: I put the oslib mailing list in cc:, it is always better to report
bugs there.
-- 
_____________________________________________________________________________
Copy this in your signature, if you think it is important:
                               N O    W A R ! ! !