On 2018-09-14 14:39, Olivier Hainque wrote:
>
>
>> On 13 Sep 2018, at 00:25, Rasmus Villemoes wrote:
>
>>> What happens on your end if you just remove the hack ?
>
>> Unfortunately, the libstdc++ build breaks:
>>
>> In file included from
>>
> On 13 Sep 2018, at 00:25, Rasmus Villemoes wrote:
>> What happens on your end if you just remove the hack ?
> Unfortunately, the libstdc++ build breaks:
>
> In file included from
> /usr/powerpc-wrs-vxworks/wind_base/target/h/regs.h:66:0,
> from
>
On 2018-09-05 11:38, Olivier Hainque wrote:
> Hi Rasmus,
>
> I think we should either do a fixinclude that would "work" for
> C and ASM (like #include vxCpu for ASM, vxTypesOld otherwise), or
> simply remove this hack (just using the fixinclude parlance here).
>
> My inclination would be for the
Hi Rasmus,
> On 3 Sep 2018, at 15:20, Rasmus Villemoes wrote:
>> How do we not get in assembly the problems we'd get in C
>> when not including vxTypesOld ?
Answering part of my own question: turns out that some pieces
included via regs.h are already taking care of the _ASMLANGUAGE
case.
>
On 2018-09-03 14:11, Olivier Hainque wrote:
> Hi Rasmus,
>
>> On 27 Jun 2018, at 16:27, Rasmus Villemoes wrote:
>> * inclhack.def (AAB_vxworks_regs_vxtypes): Guard include of
>> types/vxTypesOld.h by #ifndef _ASMLANGUAGE.
>> * fixincl.x: Regenerate.
>> ---
>>
Hi Rasmus,
> On 27 Jun 2018, at 16:27, Rasmus Villemoes wrote:
> * inclhack.def (AAB_vxworks_regs_vxtypes): Guard include of
> types/vxTypesOld.h by #ifndef _ASMLANGUAGE.
> * fixincl.x: Regenerate.
> ---
> fixincludes/inclhack.def | 2 ++
> 1 file changed, 2 insertions(+)
>
>
VxWorks' regs.h does include some files that need types defined in
vxTypesOld.h, and it does not itself include that header, directly or
indirectly. Moreover, vxTypesOld.h ends up pulling in definitions of
various cpufamily macros (from types/vxCpu.h) that are also needed
directly by regs.h.