All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jayashree D <jayashree-d@hcl.com>
To: "Wludzik, Jozef" <jozef.wludzik@linux.intel.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: OpenBMC CI issue
Date: Thu, 10 Dec 2020 06:00:36 +0000	[thread overview]
Message-ID: <SG2PR04MB3093122D52EC9467679DCF34E1CB0@SG2PR04MB3093.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <30aef9df-2a96-9b27-52ba-fcaa6628f1c2@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3255 bytes --]

Classification: Public
Thanks Jozef for your response.

From: Wludzik, Jozef <jozef.wludzik@linux.intel.com>
Sent: Thursday, December 10, 2020 12:27 AM
To: Jayashree D <jayashree-d@hcl.com>; openbmc@lists.ozlabs.org
Subject: Re: OpenBMC CI issue

[CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.]

Yes, remove compilation flag '-fno-rtti' from you makefile or cmakefile. If you use meson, then set cpp_rtti to true in default_options for project.
It is known problem in boost 1.74.0
https://github.com/openbmc/x86-power-control/issues/7<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fx86-power-control%2Fissues%2F7&data=04%7C01%7Cjayashree-d%40hcl.com%7C630126ce0db34fb9ca7108d89c742dbb%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C1%7C637431370504844646%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=to7q4ibFAShxmsYkJhHU3Qzksi9Dcdn6%2FlCT96lkPrw%3D&reserved=0>
Thanks,
Jozef
On 12/9/2020 17:00 PM, Jayashree D wrote:
Classification: Public
Hi Team,

I am getting the following error in Gerrit OpenBMC CI issues. Please provide some inputs/suggestions on this.

/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_void()’:
/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);

Regards,
Jayashree


::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________

[-- Attachment #2: Type: text/html, Size: 8037 bytes --]

  reply	other threads:[~2020-12-10  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 16:00 OpenBMC CI issue Jayashree D
2020-12-09 18:56 ` Wludzik, Jozef
2020-12-10  6:00   ` Jayashree D [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-09 15:55 Jayashree D

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=SG2PR04MB3093122D52EC9467679DCF34E1CB0@SG2PR04MB3093.apcprd04.prod.outlook.com \
    --to=jayashree-d@hcl.com \
    --cc=jozef.wludzik@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.