From: "Srinivas D.J" <srini@protocol.ece.iisc.ernet.in>
To: gcc-help@gcc.gnu.org
Subject: cross compiler for msdos: conflicting variable declarations.
Date: Wed, 25 Sep 2002 00:17:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0209251238080.32275-100000@protocol.ece.iisc.ernet.in> (raw)
Hi,
I am trying to build cross compiler for msdos on Linux machine using
djgpp headers (tools). Binutils-2.13 was built successfully, but while
building gcc-3.1.1 the following error was reported. gcc-2.96.2 was used
for compilation.
How to get around this error ?
files used were:djcrx203.zip, binutils-2.13, gcc-3.1.1
target=i386-pc-msdosdjgpp
==================================================
( last few lines of error )
if [ x"" != x ]; then \
/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/gcc/xgcc
-B/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/gcc/
-B/usr/i386-pc-msdosdjgpp/bin/ -B/usr/i386-pc-msdosdjgpp/lib/ -isystem
/usr/i386-pc-msdosdjgpp/include -c -DHAVE_CONFIG_H -g -O2
-I. -I../../../gcc-3.1.1/libiberty/../include -W -Wall -Wtraditional
-pedantic ../../../gcc-3.1.1/libiberty/cplus-dem.c -o pic/cplus-dem.o; \
else true; fi
/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/gcc/xgcc
-B/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/gcc/
-B/usr/i386-pc-msdosdjgpp/bin/ -B/usr/i386-pc-msdosdjgpp/lib/ -isystem
/usr/i386-pc-msdosdjgpp/include -c -DHAVE_CONFIG_H -g -O2
-I. -I../../../gcc-3.1.1/libiberty/../include -W -Wall -Wtraditional
-pedantic ../../../gcc-3.1.1/libiberty/cplus-dem.c
In file included from ../../../gcc-3.1.1/include/libiberty.h:48,
from ../../../gcc-3.1.1/libiberty/cplus-dem.c:54:
/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/gcc/include/stdarg.h:110: conflicting
types for `va_list'
/usr/i386-pc-msdosdjgpp/include/stdio.h:35: previous declaration of
`va_list'
make[1]: *** [cplus-dem.o] Error 1
make[1]: Leaving directory
`/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/i386-pc-msdosdjgpp/libiberty'
make: *** [all-target-libiberty] Error 2
==========================================================
/usr/i386-pc-msdosdjgpp/include/sys/djtypes.h:15:
#define __DJ_va_list typedef void *va_list;
-----
/usr/i386-pc-msdosdjgpp/include/stdio.h:35:
__DJ_va_list
#undef __DJ_va_list
#define __DJ_va_list
------
/usr/local/dosgcc/i386-pc-msdosdjgpp-gcc/gcc/include/stdarg.h:110:
#ifndef __va_list__
typedef __gnuc_va_list va_list;
#endif /* not __va_list__ */
-----
Thanks a lot
srinivas
reply other threads:[~2002-09-25 7:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0209251238080.32275-100000@protocol.ece.iisc.ernet.in \
--to=srini@protocol.ece.iisc.ernet.in \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).