All of lore.kernel.org
 help / color / mirror / Atom feed
* OpenBMC CI issue
@ 2020-12-09 16:00 Jayashree D
  2020-12-09 18:56 ` Wludzik, Jozef
  0 siblings, 1 reply; 4+ messages in thread
From: Jayashree D @ 2020-12-09 16:00 UTC (permalink / raw)
  To: openbmc

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

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: 4618 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: OpenBMC CI issue
  2020-12-09 16:00 OpenBMC CI issue Jayashree D
@ 2020-12-09 18:56 ` Wludzik, Jozef
  2020-12-10  6:00   ` Jayashree D
  0 siblings, 1 reply; 4+ messages in thread
From: Wludzik, Jozef @ 2020-12-09 18:56 UTC (permalink / raw)
  To: Jayashree D, openbmc

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

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
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: 5221 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: OpenBMC CI issue
  2020-12-09 18:56 ` Wludzik, Jozef
@ 2020-12-10  6:00   ` Jayashree D
  0 siblings, 0 replies; 4+ messages in thread
From: Jayashree D @ 2020-12-10  6:00 UTC (permalink / raw)
  To: Wludzik, Jozef, openbmc

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* OpenBMC CI issue
@ 2020-12-09 15:55 Jayashree D
  0 siblings, 0 replies; 4+ messages in thread
From: Jayashree D @ 2020-12-09 15:55 UTC (permalink / raw)
  To: openbmc; +Cc: Velumani T-ERS, HCLTech, Manikandan E

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

Classification: Internal

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: 4578 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2020-12-10  6:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-09 16:00 OpenBMC CI issue Jayashree D
2020-12-09 18:56 ` Wludzik, Jozef
2020-12-10  6:00   ` Jayashree D
  -- strict thread matches above, loose matches on Subject: below --
2020-12-09 15:55 Jayashree D

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.