openbmc / x86-power-control

Apache License 2.0
12 stars 10 forks source link

latest yocto rebase failing due to boost issues #7

Closed geissonator closed 4 years ago

geissonator commented 4 years ago

Our latest yocto update brought in a new version of boost.

https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/36615/ boost: update 1.73.0 -> 1.74.0

This seems to be causing some new issues. I believe @edtanous had looked into it a bit and mentioned the latest boost master has a fix, but it has not been released yet.

Need to either disable the boost feature causing the problem (-no-rtti ?) or send a patch to upstream yocto to go with the boost recipe to pick up the change.

geissonator commented 4 years ago

The error:

/var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp: In static member function 'static const std::type_info& boost::asio::execution::detail::any_executor_base::target_type_void()':
/var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp:811:23: error: cannot use 'typeid' with '-fno-rtti'
  811 |     return typeid(void);
      |                       ^
/var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp: In static member function 'static const std::type_info& boost::asio::execution::detail::any_executor_base::target_type_ex()':
/var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp:851:21: error: cannot use 'typeid' with '-fno-rtti'
  851 |     return typeid(Ex);
      |  
edtanous commented 4 years ago

The bug in question is here: https://github.com/chriskohlhoff/asio/issues/533

I suspect the best answer here is to simply disable -fno-rtti for the moment, and take the small increase in compile size, until boost 1.74.1 is released and merged with yocto. I've already done this on bmcweb when I found the bug.

-Ed

On Mon, Oct 5, 2020 at 8:15 AM Andrew Geissler notifications@github.com wrote:

The error:

/var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp: In static member function 'static const std::type_info& boost::asio::execution::detail::any_executor_base::target_type_void()': /var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp:811:23: error: cannot use 'typeid' with '-fno-rtti' 811 return typeid(void); ^ /var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp: In static member function 'static const std::type_info& boost::asio::execution::detail::any_executor_base::target_type_ex()': /var/lib/jenkins-slave/workspace/ci-openbmc/distro/ubuntu/label/docker-builder/target/tiogapass/build/work/arm1176jzs-openbmc-linux-gnueabi/x86-power-control/1.0+gitAUTOINC+e63dea0875-r0/recipe-sysroot/usr/include/boost/asio/execution/any_executor.hpp:851:21: error: cannot use 'typeid' with '-fno-rtti' 851 return typeid(Ex);

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openbmc/x86-power-control/issues/7#issuecomment-703698734, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAESOWOZXEQBBALJF6YBMHLSJHPHVANCNFSM4SEWD3NA .

geissonator commented 4 years ago

rtti disable put up at https://gerrit.openbmc-project.xyz/c/openbmc/x86-power-control/+/37078