fenv.h issue [Was: Patch crosstool-NG hg - Canadian cross, mingw host?.]

[Bill Pringlemeir <bpringle at sympatico dot ca>]

On 28 Oct 2010, bpringle@sympatico.ca wrote:

>> I have the same issue as this poster,

>> http://permalink.gmane.org/gmane.comp.gcc.cross-compiling/12221

> bpringlemeir@ps-bpringlemeir1:~/crosstool-NG/crosstool-ng$ hg diff
> diff -r c27380b72046 scripts/build/companion_libs/cloog.sh
> --- a/scripts/build/companion_libs/cloog.sh Sat Oct 23 23:29:46 2010 +0200
> +++ b/scripts/build/companion_libs/cloog.sh     Thu Oct 28 10:40:41 2010 -0400
> @@ -55,7 +55,8 @@
> cloog_opts+=( --enable-shared --disable-static )
> else
> cloog_opts+=( --disable-shared --enable-static )
> -        cloog_LDFLAGS='-lstdc++ -lm'
> +        cloog_opts+=( --with-host-libstdcxx='-lstdc++' )
> +        cloog_LDFLAGS='-lm'
> fi

> CFLAGS="${CT_CFLAGS_FOR_HOST}"              \

> My final compile issues seem to be related to the 'fenv.h' issues that
> are being discussed.  Or I am new to cross tools and might have made a
> config mistake.

I don't know if this is related to other 'fenv.h' issues, but I
disabled the 'pch' option and the C++ library phase completed. And a
new shiny mingw-arm cross is available on my Linux machine.  I cross
compiled a large Qt app under Wine and have it running on an
Arm926ej-s processor.  I am in the process of exporting the rootfs and
other tools to a Windows machine.

My '.config' is the same before/after disabling the pch option, so
cross tools is keeping options somewhere else?  Or rebuilding
everything corrected the issue.

Fwiw,
Bill Pringlemeir.

--
For unsubscribe information see http://sourceware.org/lists.html#faq