>From: [EMAIL PROTECTED]

>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

... So you did not use a C comiler to compile cdrecord....

The language C does not have any predefined function.
Do you get a printf.o ?

>        ==> 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.

Unless you are on Next Step which has a buggy C-compiler that does not
allow to have your own printf(), printf is definitely a macro!

In addition, I see no reason why such an #if #else
constructs should not be allowed in macro parameter lists but
it seems to be a gcc limitation with parameterized macros.
This on the other side verifies a noncompliance in GCC.

It looks that gcc 3.x is junk and you need to send a bug report
to the authors.

J�rg

 EMail:[EMAIL PROTECTED] (home) J�rg Schilling D-13353 Berlin
       [EMAIL PROTECTED]               (uni)  If you don't have iso-8859-1
       [EMAIL PROTECTED]           (work) chars I am J"org Schilling
 URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to