This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Crossed-Native Builds, Toolchain Relocation and MinGW
On Wed, Apr 26, 2006 at 06:29:46PM +0530, Ranjit Mathew wrote:
> $SYSTEM_HEADER_DIR is supposed to be "/mingw/include"
> for a native MinGW target (and since host == target, the
> build is being considered native). However, in a crossed-
> native build, I cannot have MinGW headers in this path, so
> the way I work around this problem is to additionally specify
> "--with-sysroot=$PREFIX" and extract MinGW headers into
> "$PREFIX/mingw". This lets the build and installation
> complete successfully, but when I tar this installation
> and install it on a Windows machine, GCC fails to find
> the system headers. The workaround *then* is to rename
> the "mingw" folder to "$TARGET" (i.e. i686-pc-mingw32)
> again. Needless to say, this is painful. In earlier
> releases, I used to be able to just extract the headers
> to $PREFIX/$TARGET, do the crossed-native build, install
> the compiler and then bundle this installation up to
> create a relocatable toolchain. This was the whole point
> of the article:
If you look at HEAD, you'll find a new --with-build-sysroot
option. Does that help? We added it for some very similar
configurations...
--
Daniel Jacobowitz
CodeSourcery