From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=aFo3=F4=lists.ozlabs.org=openbmc-bounces+openbmc=archiver.kernel.org@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,
	SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 8420EC433E6
	for <openbmc@archiver.kernel.org>; Thu, 24 Dec 2020 18:36:01 +0000 (UTC)
Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.kernel.org (Postfix) with ESMTPS id B30CD22512
	for <openbmc@archiver.kernel.org>; Thu, 24 Dec 2020 18:36:00 +0000 (UTC)
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B30CD22512
Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=yadro.com
Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org
Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3])
	by lists.ozlabs.org (Postfix) with ESMTP id 4D1zKp5cVdzDqLv
	for <openbmc@archiver.kernel.org>; Fri, 25 Dec 2020 05:35:58 +1100 (AEDT)
Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized)
 smtp.mailfrom=yadro.com (client-ip=89.207.88.252; helo=mta-01.yadro.com;
 envelope-from=a.kartashev@yadro.com; receiver=<UNKNOWN>)
Authentication-Results: lists.ozlabs.org;
 dmarc=pass (p=none dis=none) header.from=yadro.com
Authentication-Results: lists.ozlabs.org; dkim=pass (1024-bit key;
 unprotected) header.d=yadro.com header.i=@yadro.com header.a=rsa-sha256
 header.s=mta-01 header.b=I62Z/5eQ; dkim-atps=neutral
Received: from mta-01.yadro.com (mta-02.yadro.com [89.207.88.252])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.ozlabs.org (Postfix) with ESMTPS id 4D1zJP12RqzDq94
 for <openbmc@lists.ozlabs.org>; Fri, 25 Dec 2020 05:34:44 +1100 (AEDT)
Received: from localhost (unknown [127.0.0.1])
 by mta-01.yadro.com (Postfix) with ESMTP id B3AE141386;
 Thu, 24 Dec 2020 18:34:41 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yadro.com; h=
 content-transfer-encoding:mime-version:user-agent:content-type
 :content-type:organization:references:in-reply-to:date:date:from
 :from:subject:subject:message-id:received:received:received; s=
 mta-01; t=1608834880; x=1610649281; bh=BA8vnkQYwJUXx+8guevoReAV/
 v5iqVCo/ktvhN/8lFw=; b=I62Z/5eQkRtT1jCadfK77L8krNJYeKCxpyvp+81k4
 deQz8L6MD8YM9Xn4702KiAerrXzgzI75kGl0WEdi7FS/dOMPPgDYQKTgrAS16Qte
 0sgCrGb1n035D7NZ1WvnmrqG3WcZOJQ+xhDLlQkOnRM7bfYd0nKD3GlsaIEcrKef
 CA=
X-Virus-Scanned: amavisd-new at yadro.com
Received: from mta-01.yadro.com ([127.0.0.1])
 by localhost (mta-01.yadro.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id teq1h_jqSK4b; Thu, 24 Dec 2020 21:34:40 +0300 (MSK)
Received: from T-EXCH-03.corp.yadro.com (t-exch-03.corp.yadro.com
 [172.17.100.103])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
 (No client certificate requested)
 by mta-01.yadro.com (Postfix) with ESMTPS id 62A1A41381;
 Thu, 24 Dec 2020 21:34:40 +0300 (MSK)
Received: from [10.199.0.21] (10.199.0.21) by T-EXCH-03.corp.yadro.com
 (172.17.100.103) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Thu, 24
 Dec 2020 21:34:39 +0300
Message-ID: <0759e6524c910c8d24f1453dbbe226bc3460e588.camel@yadro.com>
Subject: Re: peci-pcie CI issues
From: Andrei Kartashev <a.kartashev@yadro.com>
To: Ed Tanous <ed@tanous.net>, Patrick Williams <patrick@stwcx.xyz>
Date: Thu, 24 Dec 2020 21:34:38 +0300
In-Reply-To: <CACWQX82quUYK+r0BkDqT0ZABXgRPj797Wwr8Joov05w8tCLwuA@mail.gmail.com>
References: <6c2c44435e704f6eee95b7e35cbc39ccfae32b62.camel@yadro.com>
 <EC305987-22B3-40D2-86A6-4FF95B395956@stwcx.xyz>
 <CACWQX82quUYK+r0BkDqT0ZABXgRPj797Wwr8Joov05w8tCLwuA@mail.gmail.com>
Organization: YADRO
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.199.0.21]
X-ClientProxiedBy: T-EXCH-01.corp.yadro.com (172.17.10.101) To
 T-EXCH-03.corp.yadro.com (172.17.100.103)
X-BeenThere: openbmc@lists.ozlabs.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Development list for OpenBMC <openbmc.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/openbmc>,
 <mailto:openbmc-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/openbmc/>
List-Post: <mailto:openbmc@lists.ozlabs.org>
List-Help: <mailto:openbmc-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/openbmc>,
 <mailto:openbmc-request@lists.ozlabs.org?subject=subscribe>
Cc: "jason.m.bills" <jason.m.bills@linux.intel.com>,
 openbmc <openbmc@lists.ozlabs.org>
Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org
Sender: "openbmc"
 <openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org>

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