Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Tue, 17 Aug 1999 14:15:33 -0700 From: wayne roberts To: cygwin AT sourceware DOT cygnus DOT com Subject: mingw32-2.95 stdarg.h blues Message-ID: <19990817141533.A6418@cx983858-b.orng1.occa.home.com> Reply-To: wroberts1 AT home DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us mingw32-2.95 has two stdarg.h: lib/gcc-lib/i386-mingw32/2.95/include/stdarg.h i386-mingw32/include/stdarg.h Each has its own definition of va_start macro. The one in i386-mingw32/include works, the mingw32 in windows uses it. However, i built mingw cross compiler in linux and it mysteriously uses the one under the gcc-lib dir: cause a void pointer casting error from __gnuc_va_list. the va_start that works is: #define va_start(ap, pN) ((ap) = ((va_list) (&pN) + __va_argsiz(pN))) which has no __gnuc_va_list void pointer cast present. So what causes my cross compiler to grab a different header than the one running in windows? -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com