Re: compiler error? (RE: please review wip/cc65)

[email protected]
Newsgroups gmane.os.netbsd.devel.pkgsrc.wip.review,gmane.os.netbsd.devel.pkgsrc.wip.general
Message-ID <[email protected]>
=> [email protected] <mailto:[email protected]> wrote:
=>> In file included from strbuf.c:42:
=>> va_copy.h:48:2: error: #error "The compiler is broken!"
=>> In file included from xsprintf.c:46:
=>> va_copy.h:48:2: error: #error "The compiler is broken!"
=>> gmake[2]: *** [depend] Error 1
=>> gmake[2]: Leaving directory
=>> `/usr/pkgsrc/wip/cc65/work.x86_64/cc65-2.12.0/src/common'
=>> gmake[1]: *** [all] Error 2
=>
=> (Changing group. Please remove pkgsrc-wip-review from replies.)
=>
=> The following comment was the response I received from the developer:
=>
=> {{{ This means that the compiler claims to be compliant to an ANSI or ISO
=> standard before C99 but defines va_copy anyway. If the former is true,
=> va_copy is no reserved identifier and must not be defined by the compiler.
=> At least this is my interpretation of the standard is how other compilers
=> implement it. Maybe someone active in -BSD development can comment on it.
=> }}}

   A quick search shows that NetBSD is setting the following in stdarg.h:

#if !defined(_ANSI_SOURCE) &&                                           \
    (defined(_ISOC99_SOURCE) || (__STDC_VERSION__ - 0) >= 199901L ||    \
     defined(_NETBSD_SOURCE))
#define va_copy(dest, src)      __va_copy((dest), (src))
#endif

   I haven't yet checked to see if this is actually included, or which
macros were set.

                                      Gary Duzan




-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.