Re: [RFC PATCH 1/6] vxworks: add target/h/wrn/coreip to the set of system include paths

2018-06-14 Thread Olivier Hainque
Hi Rasmus, > On 13 Jun 2018, at 08:46, Rasmus Villemoes wrote: > >> This include path part alone looks sensible. I'd still like to >> evaluate how it fares in a environment where many of there variations >> are exercised, and I'm not quite done with this yet. > > Thanks, I do hope for careful

Re: [RFC PATCH 1/6] vxworks: add target/h/wrn/coreip to the set of system include paths

2018-06-13 Thread Rasmus Villemoes
On 2018-06-12 23:34, Olivier Hainque wrote: > > >> On 12 Jun 2018, at 23:12, Jeff Law wrote: >> >> I'm going to defer to Olivier on all 6 parts of this kit. He knows >> vxworks far better than I. > > No pb. I haven't forgotten about this :) > > As I mentioned on another > thread, exceptions

Re: [RFC PATCH 1/6] vxworks: add target/h/wrn/coreip to the set of system include paths

2018-06-12 Thread Olivier Hainque
> On 12 Jun 2018, at 23:12, Jeff Law wrote: > > I'm going to defer to Olivier on all 6 parts of this kit. He knows > vxworks far better than I. No pb. I haven't forgotten about this :) As I mentioned on another thread, exceptions on VxWorks is an intricate nest of multiple parameters when

Re: [RFC PATCH 1/6] vxworks: add target/h/wrn/coreip to the set of system include paths

2018-06-12 Thread Jeff Law
On 06/04/2018 08:46 AM, Rasmus Villemoes wrote: > 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 +=