]> gcc.gnu.org Git - gcc.git/commit
vxworks: add target/h/wrn/coreip to the set of system include paths
authorRasmus Villemoes <rv@rasmusvillemoes.dk>
Tue, 21 Aug 2018 08:47:41 +0000 (10:47 +0200)
committerRasmus Villemoes <villemoes@gcc.gnu.org>
Tue, 21 Aug 2018 08:47:41 +0000 (08:47 +0000)
commit6b19ff66a82ca0029060dbfec351f83d8d877102
tree2421c49f24706fa45aca907ce1eda30b8c880a0a
parent6b2ffa6a4245fc0376c1e0f9bbcbb38b2d862425
vxworks: add target/h/wrn/coreip to the set of system include paths

In order to build crtstuff.c, I need to ensure the headers in
target/h/wrn/coreip are also searched. Of course, that can be done
similar to how wrn/coreip gets manually added for libgcc, e.g. by adding

  CRTSTUFF_T_CFLAGS += -I$(WIND_BASE)/target/h -I$(WIND_BASE)/target/h/wrn/coreip

But without target/h/wrn/coreip in the default search path, all
user-code that include <unistd.h> (crtstuff.c just being one such
example) will have to manually add an -isystem
flag adding the wrn/coreip directory: unistd.h include ioLib.h, which
has

#include "net/uio.h"

and that header is found in target/h/wrn/coreip. In other words, the
VxWorks system headers (at least for VxWorks 5.5) are written in a way
that assumes wrn/coreip is in the search path, so I think it makes sense
to have that by default.

It will change the search order for existing setups that pass
-I.../target/h/wrn/coreip (without -nostdinc), since that flag will now
be ignored. I can't know whether that will break anything, but I do
believe it makes sense to have the defaults actually usable without
expecting all invocations to add -I/-isystem flags.

From-SVN: r263689
gcc/ChangeLog
gcc/config/vxworks.h
This page took 0.060345 seconds and 5 git commands to generate.