Please read README and look to inclhack.def for examples approximating the kind of testing you are interested in doing. "test -r vxWorks.h" is a pointless test if you configure the fix to apply only to a file named vxWorks.h.
On Wed, Jun 6, 2012 at 9:33 AM, rbmj <r...@verizon.net> wrote: > Hi everyone, > > This patch series is the result of this [1] thread about fixincludes on > VxWorks. It resolves bugs 53457 and 53378, and a few other issues that > previously required manual intervention to fix for VxWorks header files. > > The fixes are tested and work correctly both with make stmp-fixinc in gcc > and make check in fixincludes. > > The initial hack (which is not the most elegant solution but isn't quite as > pessimal as disabling everything entirely) does not break anything on both a > cross build to powerpc-wrs-vxworks and a bootstrap build on > x86_64-unknown-linux-gnu. > > Any comments are appreciated. Also, I don't have commit access. > > CC'ing Nathan Sidwell and Bruce Korb, as MAINTAINERS says you're the VxWorks > and fixincludes maintainers, respectively. > > Thanks, > > Robert Mason > > [1] http://gcc.gnu.org/ml/gcc-help/2012-05/msg00172.html
