Top Document: comp.sys.hp.hpux FAQ Previous Document: 6.2.4 Why do I get "_builtin_va_start" undefined when I build with gcc? Next Document: 6.2.6 Why do I get the error "*Initialization*:1: missing token-sequence in `#assert'" when I compile with gcc? See reader questions & answers on this topic! - Help others by sharing your knowledge The C compiler dislikes this construct in ANSI mode: x = FLT_MIN; /* <---- warning here */ The problem is that the ANSI mode (_PROTOTYPES) version of FLT_MIN/FLT_MAX in <float.h> end their constants with an F, which seems to upset the compiler. The workaround is to temporarily undef _PROTOTYPES around the <float.h> inclusion: #ifdef _PROTOTYPES #undef _PROTOTYPES #include <float.h> #define _PROTOTYPES #else #include <float.h> #endif User Contributions:Top Document: comp.sys.hp.hpux FAQ Previous Document: 6.2.4 Why do I get "_builtin_va_start" undefined when I build with gcc? Next Document: 6.2.6 Why do I get the error "*Initialization*:1: missing token-sequence in `#assert'" when I compile with gcc? Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: hpux.faq@gmail.com
Last Update March 27 2014 @ 02:11 PM
|
Comment about this article, ask questions, or add new information about this topic: