|
The <varargs.h> and <stdarg.h> include files define va_start in terms of this function, which is built-in on the HP C compiler. If you're using GCC you should be picking up include files from the gcc library directory. These include files do the right thing for both GCC and HP C. More often than not these files were never installed, or someone has placed a copy of varargs.h/stdarg.h into /usr/local/include (gcc searches there first). When all else fails, you can replace the definition of va_start as follows, depending on whether you are using varargs or stdarg (K&R or ANSI, respectively). #include <varargs.h> #ifdef __hppa #undef va_start #define va_start(a) ((a)=(char *)&va_alist+4) #endif #include <stdarg.h> #ifdef __hppa #undef va_start #define va_start(a,b) ((a)=(va_list)&(b)) #endif For <varargs.h>, this replacement should always work. For <stdarg.h>, this replacement will work unless the last fixed parameter ("b" in the call to va_start) is a structure larger than 8 bytes. ...
more
|
How come I get "_builtin_va_start" undefined when I build with gcc?
Related Questions
- A. GCC 4.3.2 requires libraries built with GCC 4.3 or later. In particular, users should load the modules xt- ...
- You probably had an error somewhere, most likely in the plot() method, and you didn't check for it. See the ...
- You're probably linking against a different version of libpcap than the one used to build libnids (this is ...
- If it has undefined slope, there is no y-intercept. The line is X=-9.
- If you are running in a Terminal Server environment, Jaws PDF Server supports Terminal Services on Windows ...