Stephen Warren wrote:
Phil Dibowitz wrote:
It's so weird I don't get the same behavior...
[variadic macros error from gcc]
Yes indeed.
I installed a Debian sid chroot on my Fedora 8 system using the
debootstrap utility, and installed the gcc-4.3 and g++-4.3 packages
using aptitude
On Sun, March 30, 2008 11:41 pm, Phil Dibowitz wrote:
And again, you missed what I said about declarations not at the top. This
is why we use -ansi -pedantic-errors:
[EMAIL PROTECTED] tmp]$ gcc -std=c99 foo.c
[EMAIL PROTECTED] tmp]$ gcc -std=c99 -pedantic-errors foo.c
[EMAIL PROTECTED] tmp]$
Stephen Warren wrote:
* It certainly won't remove the warning about strdup not being prototyped
(that's due to -ansi), which is a warning for me, but I believe an error
on gcc-4.3 (hence why I submitted the patch for libconcord to add a bunch
of headers to help packaging libconcord on Fedora 9
Stephen Warren wrote:
Phil Dibowitz wrote:
Stephen Warren wrote:
* It certainly won't remove the warning about strdup not being prototyped
(that's due to -ansi), which is a warning for me, but I believe an error
on gcc-4.3 (hence why I submitted the patch for libconcord to add a bunch
of
Stephen Warren wrote:
Phil Dibowitz wrote:
Stephen Warren wrote:
* It certainly won't remove the warning about strdup not being prototyped
(that's due to -ansi), which is a warning for me, but I believe an error
on gcc-4.3 (hence why I submitted the patch for libconcord to add a bunch
of
Latest libconcord.h contains:
static inline void debug(const char *str) {}
This causes a build failure because inline isn't a valid keyword in
standard ANSI C. Simply removing inline seems to fix the problem.
-
Check out
Phil Dibowitz wrote:
Stephen Warren wrote:
Latest libconcord.h contains:
static inline void debug(const char *str) {}
This causes a build failure because inline isn't a valid keyword in
standard ANSI C. Simply removing inline seems to fix the problem.
Already fixed...
I still get this:
Stephen Warren wrote:
Phil Dibowitz wrote:
Stephen Warren wrote:
Latest libconcord.h contains:
static inline void debug(const char *str) {}
This causes a build failure because inline isn't a valid keyword in
standard ANSI C. Simply removing inline seems to fix the problem.
Already
Stephen Warren wrote:
I propose we replace -ansi -pedantic-errors with -std=c99.
Sorry, just remove -ansi -pedantic-errors and don't add -std=c99;
the variadic macro works with -std=c99, but the strdup prototype still
isn't present unless we just remove all the standard-selection options.
Stephen Warren wrote:
Stephen Warren wrote:
I propose we replace -ansi -pedantic-errors with -std=c99.
Sorry, just remove -ansi -pedantic-errors and don't add -std=c99;
the variadic macro works with -std=c99, but the strdup prototype still
isn't present unless we just remove all the
Phil Dibowitz wrote:
Stephen Warren wrote:
Stephen Warren wrote:
I propose we replace -ansi -pedantic-errors with -std=c99.
Sorry, just remove -ansi -pedantic-errors and don't add -std=c99;
the variadic macro works with -std=c99, but the strdup prototype still
isn't present unless we just
Stephen Warren wrote:
Phil Dibowitz wrote:
Stephen Warren wrote:
Stephen Warren wrote:
I propose we replace -ansi -pedantic-errors with -std=c99.
Sorry, just remove -ansi -pedantic-errors and don't add -std=c99;
the variadic macro works with -std=c99, but the strdup prototype still
isn't
12 matches
Mail list logo
