On 19 Mar, [EMAIL PROTECTED] wrote:
> Please run the libscg conformance test on your platform.
> I am interested in test results for other platforms.
>
> If there are no bugs, then this release will become 1.10 final.
>
Thanks for this release.
I've some (minor) problems when building it on Linux (Gmake.linux)
==> COMPILING "OBJ/i686-linux-cc/printf.o"
printf.c:67: parse error before "const"
printf.c:73: warning: conflicting types for built-in function `fprintf'
printf.c: In function `fprintf':
printf.c:82: `form' undeclared (first use in this function)
printf.c:82: (Each undeclared identifier is reported only once
printf.c:82: for each function it appears in.)
printf.c:82: `va_start' used in function with fixed args
printf.c: At top level:
printf.c:102: conflicting types for `fprintf'
printf.c:73: previous declaration of `fprintf' <=== within system headers
Seems to harmless, since the system provided fprintf gets linked later
on
==> COMPILING "OBJ/i686-linux-cc/cdrecord.o"
cdrecord.c:249:1: directives may not be used inside a macro argument
cdrecord.c:249:1: unterminated argument list invoking macro "printf"
cdrecord.c: In function `main':
cdrecord.c:252: parse error before string constant
cdrecord.c:255: parse error before ')' token
This is compiled with (very) recent gcc (3.1.x). Just duplicated
the code such that the complete macro is contained within
an #if or #else part solves the problem.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
Institute of Technology, RWTH Aachen
D 52056 Aachen, Germany
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
