openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Kartashev <a.kartashev@yadro.com>
To: Ed Tanous <ed@tanous.net>, Patrick Williams <patrick@stwcx.xyz>
Cc: "jason.m.bills" <jason.m.bills@linux.intel.com>,
	openbmc <openbmc@lists.ozlabs.org>
Subject: Re: peci-pcie CI issues
Date: Thu, 24 Dec 2020 21:34:38 +0300	[thread overview]
Message-ID: <0759e6524c910c8d24f1453dbbe226bc3460e588.camel@yadro.com> (raw)
In-Reply-To: <CACWQX82quUYK+r0BkDqT0ZABXgRPj797Wwr8Joov05w8tCLwuA@mail.gmail.com>

Well, then probably we can wait.
How far this could happens?

On Thu, 2020-12-24 at 10:23 -0800, Ed Tanous wrote:
> On Thu, Dec 24, 2020 at 10:07 AM Patrick Williams <patrick@stwcx.xyz>
> wrote:
> > We have had this issue with a number of repositories lately. The
> > most recent version of boost::asio does not allow -fno-rtti.  The
> > makefile needs to be changed to no longer force this option.
> 
> Or, as another option, just wait until boost 1.75.0 lands in yocto
> master and subsequent openbmc bump.  It was released a couple weeks
> ago and fixes this issue.  We'll likely be adding the no-rtti flags
> back to most of the repos shortly after that.
> 
> > Sent from my iPhone
> > 
> > > On Dec 24, 2020, at 9:48 AM, Andrei Kartashev <
> > > a.kartashev@yadro.com> wrote:
> > > 
> > > Hello Jason,
> > > 
> > > I push several patches to peci-pcie repo, but looks like CI
> > > broken
> > > there. Could you take a look on how to fix CI?
> > > 
> > > [ 90%] Building CXX object CMakeFiles/peci-
> > > pcie.dir/src/peci_pcie.cpp.o
> > > In file included from
> > > /usr/local/include/boost/asio/execution.hpp:19,
> > >                 from
> > > /usr/local/include/boost/asio/system_executor.hpp:20,
> > >                 from
> > > /usr/local/include/boost/asio/associated_executor.hpp:22,
> > >                 from
> > > /usr/local/include/boost/asio/detail/bind_handler.hpp:20,
> > >                 from
> > > /usr/local/include/boost/asio/detail/wrapped_handler.hpp:18,
> > >                 from
> > > /usr/local/include/boost/asio/io_context.hpp:23,
> > >                 from
> > > /usr/local/include/boost/asio/io_service.hpp:18,
> > >                 from /home/jenkins-op/workspace/ci-
> > > repository/openbmc/peci-pcie/src/peci_pcie.cpp:22:
> > > /usr/local/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_vo
> > > id()’:
> > > /usr/local/include/boost/asio/execution/any_executor.hpp:811:23:
> > > error: cannot use ‘typeid’ with ‘-fno-rtti’
> > >  811 |     return typeid(void);
> > >      |                       ^
> > > /usr/local/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
> > > ()’:
> > > /usr/local/include/boost/asio/execution/any_executor.hpp:851:21:
> > > error: cannot use ‘typeid’ with ‘-fno-rtti’
> > >  851 |     return typeid(Ex);
> > >      |                     ^
> > > 
> > > --
> > > Best regards,
> > > Andrei Kartashev
> > > 
> > > 
-- 
Best regards,
Andrei Kartashev



  reply	other threads:[~2020-12-24 18:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 15:47 peci-pcie CI issues Andrei Kartashev
2020-12-24 18:05 ` Patrick Williams
2020-12-24 18:23   ` Ed Tanous
2020-12-24 18:34     ` Andrei Kartashev [this message]
2020-12-24 18:53       ` Ed Tanous
2021-01-12  0:08         ` Bills, Jason M
2021-01-12 19:10           ` Andrew Geissler
2021-02-10 10:04     ` Andrei Kartashev
2021-02-10 12:19       ` Patrick Williams
2021-02-10 16:07         ` Bills, Jason M
2021-02-10 16:22           ` Andrei Kartashev
2021-02-11 18:42             ` Andrei Kartashev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0759e6524c910c8d24f1453dbbe226bc3460e588.camel@yadro.com \
    --to=a.kartashev@yadro.com \
    --cc=ed@tanous.net \
    --cc=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).