Move context and coroutine
Yocto upstream moved context and coroutine directly into BOOST_LIBS,
which means that they're not added back for our arm variant.
https://github.com/lgirdk/poky/commit/624262541605c476f5a0bd415b08d00379c15b00
This causes our build to fail with "cannot find -lboost_coroutine"
errors. This should resolve it.
Tested:
Fixing CI break. No functional testing done.
(From meta-phosphor rev: 6be1787fdc13405fa9daa6755c28534bbcaa7458)
Signed-off-by: Ed Tanous <ed@tanous.net>
Change-Id: I60d7bb8ea25a08bfdb399f8addfaf560fd7a7b7c
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/meta-phosphor/recipes-support/boost/boost_%.bbappend b/meta-phosphor/recipes-support/boost/boost_%.bbappend
index b614346..fabb7f5 100644
--- a/meta-phosphor/recipes-support/boost/boost_%.bbappend
+++ b/meta-phosphor/recipes-support/boost/boost_%.bbappend
@@ -1,12 +1,10 @@
#This is largely to improve our build times by not building or installing
-#modules that OpenBMC does not use by our coding standard. Another thing to
-#note is that for most targets, coroutine and context libraries are also added
-#with a BOOST_LIBS_append_<platform> for most targets. Chrono/Thread should not
-#be relied directly, but are required dependencies of context and coroutine.
-#See the relevant portion of the openbmc coding standard with regards to boost
-#libraries
+#modules that OpenBMC does not use by our coding standard. Chrono and Thread
+#should not be relied directly, but are required dependencies of context and
+#coroutine at build time. See the relevant portion of the openbmc coding
+#standard with regards to boost libraries
#
#https://github.com/openbmc/docs/blob/master/cpp-style-and-conventions.md#boost
#
-#BOOST_LIBS_openbmc-phosphor = "chrono thread"
+BOOST_LIBS_openbmc-phosphor = "chrono context coroutine thread"