fenv.h not found?
Andy Gibbs
andyg1001@hotmail.co.uk
Thu Oct 28 06:37:00 GMT 2010
On Tuesday, October 19, 2010 9:22 AM, Arnaud Lacombe wrote:
> Hi,
> [... snip ...]
>
>>> this looks odd. These last two `fenv.h' from GCC generally ends up in
>>> %SYSROOT%/include/c++/%GCC_VERSION%/, but not in your case. EGlibc
>>> header gets installed:
>>>
>>> [ALL ] /opt/cross/platforms/foo/xtools-build/tools/bin/install -c
>>> -m 644 ../sysdeps/powerpc/bits/fenv.h
>>> /opt/cross/platforms/foo/xtools/powerpc-e500v2-linux-gnuspe//sys-root/usr/include/bits/fenv.h
>>>
>>> then is overwritten by gcc:
>>>
>>> c_compatibility_headers_install='/opt/cross/platforms/foo/xtools-build/src/gcc-4.5.1/libstdc++-v3/include/c_compatibility/complex.h
>>> /opt/cross/platforms/foo/xtools-build/src/gcc-4.5.1/libstdc++-v3/include/c_compatibility/fenv.h
>>> /opt/cross/platforms/foo/xtools-build/src/gcc-4.5.1/libstdc++-v3/include/c_compatibility/tgmath.h
>>> /opt/cross/platforms/foo/xtools-build/src/gcc-4.5.1/libstdc++-v3/include/c_compatibility/stdatomic.h';
>>> for file in $c_compatibility_headers_install; do
>>> /opt/cross/platforms/foo/xtools-build/tools/bin/install -c -m 644
>>> $file
>>> /opt/cross/platforms/foo/xtools/powerpc-e500v2-linux-gnuspe//sys-root/usr/include;
>>> done
>>>
>>> - Arnaud
>>>
>
> [... snip ...]
>hum, Yann's patch (which ) looks broken:
>
>+ if [ "${CT_CC_LANG_CXX}" = "y" ]; then
>+
>extra_config+=("--with-gxx-include-dir=${CT_SYSROOT_DIR}/usr/include")
>+ fi
>+
>
>"${CT_SYSROOT_DIR}/usr/include" is "${CT_HEADERS_DIR}" where the libc
>is told to install its headers...
>
> [... snip ...]
Hello,
I hope nobody minds me adding my 2 cents... :o)
I built a cross-toolchain for powerpc with gcc 4.5.1, eglibc 2.12 and had
the problem mentioned in Arnaud's post above re eglibc's fenv.h being
overwritten with gcc's one. This meant it failed to compile Qt, since gcc's
fenv.h used an #include_next directive and it couldn't find the necessary
fenv.h file in the include path. Rolling back the patch mentioned above,
and also the change where the symlink path was deleted (see
http://sourceware.org/ml/crossgcc/2010-10/msg00149.html) solved the problem
for me.
Thanks Arnaud!
Andy
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list