From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10305081310.AA22228@clio.rice.edu>
Subject:	Re: DXE3 in DJGPP CVS breaks cross-compiling
To:	djgpp-workers AT delorie DOT com
Date:	Thu, 8 May 2003 08:10:26 -0500 (CDT)
In-Reply-To:	<200305081426.01388.pavenis@latnet.lv> from "Andris Pavenis" at May 08, 2003 02:26:01 PM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 3) After I put bin2c on path, got linker error messages:
> 
> gcc -g -O2 -I ../../include -DDXE_LD=\"i586-pc-msdosdjgpp-ld\" dxe3gen.c -o ../../hostbin/dxegen.exe
> In file included from dxe3gen.c:23:
> ../../include/string.h:28: warning: conflicting types for built-in function `memcmp'
> ../../include/string.h:29: warning: conflicting types for built-in function `memcpy'
> ../../include/string.h:31: warning: conflicting types for built-in function `memset'
> ../../include/string.h:40: warning: conflicting types for built-in function `strncat'
> ../../include/string.h:41: warning: conflicting types for built-in function `strncmp'
> ../../include/string.h:42: warning: conflicting types for built-in function `strncpy'
> /tmp/ccLEBaD8.o(.text+0x722): In function `process_args':
> /disk2/cvs/djgpp/build/djgpp/src/dxe/dxe3gen.c:240: undefined reference to `__dj_stderr'

It turns out all of these are because we have compiled against the DJGPP 
headers instead of the Linux headers.  This can be fixed by removing the
-I ../../include - but then it can't find dxe.h

It appears this was "fixed" in the old dxegen by hard coding the location 
of dxe.h (which tied dxegen to the src directory structure).  Since dxe3gen
is currently also used "separately" - any suggestions on getting it to
include only the one file without all the other headers?

- Raw text -