Describe the bug
The build of the master branch is broken on macOS 10.15 .
To Reproduce
Build on macOS, there is a compilation failure:
~
2019-12-19T02:37:52.8733920Z [ 70%] Building CXX object src/yarprobotinterface/CMakeFiles/yarprobotinterface.dir/Module.cpp.o
2019-12-19T02:37:53.5398600Z /Users/runner/runners/2.163.1/work/robotology-superbuild/robotology-superbuild/robotology/YARP/src/yarprobotinterface/Module.cpp:74:25: error: member reference type 'struct __darwin_mcontext64 *' is a pointer; did you mean to use '->'?
2019-12-19T02:37:53.5399210Z context->uc_mcontext.gregs[REG_RIP]++;
2019-12-19T02:37:53.5399320Z ~~~~^
2019-12-19T02:37:53.5399710Z ->
2019-12-19T02:37:53.5420750Z /Users/runner/runners/2.163.1/work/robotology-superbuild/robotology-superbuild/robotology/YARP/src/yarprobotinterface/Module.cpp:74:26: error: no member named 'gregs' in '__darwin_mcontext64'
2019-12-19T02:37:53.5421280Z context->uc_mcontext.gregs[REG_RIP]++;
2019-12-19T02:37:53.5421390Z ~~~~~~ ^
2019-12-19T02:37:53.5467020Z /Users/runner/runners/2.163.1/work/robotology-superbuild/robotology-superbuild/robotology/YARP/src/yarprobotinterface/Module.cpp:74:32: error: use of undeclared identifier 'REG_RIP'
2019-12-19T02:37:53.5467550Z context->uc_mcontext.gregs[REG_RIP]++;
2019-12-19T02:37:53.5467650Z ^
2019-12-19T02:37:53.5871150Z 3 errors generated.
~~~
Expected behavior
The compilation to be successful.
Configuration (please complete the following information):
Additional context
Link to the failed build in GitHub Actions: https://github.com/robotology/robotology-superbuild/runs/355635206 .
I guess the related commit is https://github.com/robotology/yarp/commit/93238fb6d3836fee59c467796e4c607fe18adea1 .
Quite strange error, I will handle next week.
yarp-3.3 compiles?
Quite strange error, I will handle next week.
yarp-3.3compiles?
Yes, the commit that introduced that code is https://github.com/robotology/yarp/commit/93238fb6d3836fee59c467796e4c607fe18adea1 , and it was not added to the yarp-3.3 branch.
All the macos builds are now failing :boom: :rage: :boom:
Ups, I think that's my fault
Should be fixed by bc074eb6059140ddacc24b313da94b507d07ef05