Re: Why is fixincludes not doing anything?

[Ian Lance Taylor <iant@xxxxxxxxxx>]

rbmj <rbmj@xxxxxxxxxxx> writes:

> Looking at mkfixinc.sh:
>
> case $machine in
>     i?86-*-cygwin* | \
>     i?86-*-mingw32* | \
>     x86_64-*-mingw32* | \
>     i?86-*-interix* | \
>     *-*-vxworks* | \
>     powerpc-*-eabisim* | \
>     powerpc-*-eabi*    | \
>     powerpc-*-rtems*   | \
>     powerpcle-*-eabisim* | \
>     powerpcle-*-eabi* )
>     #  IF there is no include fixing,
>     #  THEN create a no-op fixer and exit
>     (echo "#! /bin/sh" ; echo "exit 0" ) > ${target}
>         ;;
>
>     *)
>     cat < ${srcdir}/fixinc.in > ${target} || exit 1
>     ;;
> esac
>
> That looks like the problem.
>
> So, new question- why is vxWorks disabled from include fixing?

Good job tracking it down.

This is the patch:

http://gcc.gnu.org/ml/gcc-patches/2006-10/msg00361.html

This is where it was approved:

http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00717.html

So now at least you have some people to ask.

Ian