This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Tue May 28 22:17:32 2024 >From mailfetcher Tue Mar 21 22:40:25 2023 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on pi4 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_NONE,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Authentication-Results: pi4.bmw12.nl; dmarc=none (p=none dis=none) header.from=canb.auug.org.au Authentication-Results: pi4.bmw12.nl; dkim=pass (Good 2048 bit rsa-sha256 signature) header.d=canb.auug.org.au header.a=rsa-sha256 Authentication-Results: pi4.bmw12.nl; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=2620:137:e000::1:20; helo=out1.vger.email; envelope-from=linux-kernel-owner@vger.kernel.org; receiver=) Received: from secure.jasper.es [188.166.10.231] by 1dc7d414a5be with IMAP (fetchmail-6.3.26) for (single-drop); Tue, 21 Mar 2023 22:40:25 +0100 (CET) Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by pi4.bmw12.nl (Postfix) with ESMTP id B73473F053 for ; Tue, 21 Mar 2023 22:40:22 +0100 (CET) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229487AbjCUVkK (ORCPT ); Tue, 21 Mar 2023 17:40:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34096 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229555AbjCUVkH (ORCPT ); Tue, 21 Mar 2023 17 Received: from gandalf.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A5F524BC9; Tue, 21 Mar 2023 14:39:59 -0700 (PDT) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requ DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canb.auug.org.au; s=201702; t=1679434797; bh=iUyM8WXSWONpbzj8lCsJZATCk3ti1xQ41f6XXkGrF30=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=IbGsVeC3SSBgYcmA3bZyGo/Bgy5fRAL9tF8iBd Date: Wed, 22 Mar 2023 08:39:56 +1100 From: Stephen Rothwell To: Arnaldo Carvalho de Melo Cc: Linux Kernel Mailing List , Linux Next Mailing List , Ian Rogers , Subject: Re: linux-next: build failure after merge of the perf tree Message-Id: <20230322083956.5c051777@canb.auug.org.au> In-Reply-To: <20230317095025.49aa34f9@canb.auug.org.au> References: <20230317095025.49aa34f9@canb.auug.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/NYRY2U39Yzj5UUJxYYd_bFw"; protocol="application/pgp-signature"; micalg=pgp-sha256 Precedence: bulk List-Id: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/NYRY2U39Yzj5UUJxYYd_bFw Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, On Fri, 17 Mar 2023 09:50:25 +1100 Stephen Rothwell = wrote: > > After merging the perf tree, today's linux-next build (native perf) > failed like this: >=20 > Auto-detecting system features: > ... clang-bpf-co-re: [ =1B[32mon=1B[m ] > ... llvm: [ =1B[31mOFF=1B[m ] > ... libcap: [ =1B[32mon=1B[m ] > ... libbfd: [ =1B[32mon=1B[m ] >=20 > make[1]: *** Deleting file '/home/sfr/next/perf/util/bpf_skel/vmlinux.h' > libbpf: failed to find '.BTF' ELF section in /boot/vmlinux-6.0.0-5-powerp= c64le > Error: failed to load BTF from /boot/vmlinux-6.0.0-5-powerpc64le: No data= available > make[1]: *** [Makefile.perf:1075: /home/sfr/next/perf/util/bpf_skel/vmlin= ux.h] Error 195 > make[1]: *** Waiting for unfinished jobs.... > make: *** [Makefile.perf:236: sub-make] Error 2 > Command exited with non-zero status 2 >=20 > To be clear this is a native build of perf on a PPC64le host using this > command line: >=20 > make -C tools/perf -f Makefile.perf -s -O -j60 O=3D../perf EXTRA_CFLAGS= =3D-Wno-psabi >=20 > (I could probably remove the EXTRA_CLFAGS now that I am building with > gcc 12.2) >=20 > I don't know which commit caused this. >=20 > I have used the perf tree from next-20230316 for today. I am still getting this build failure. --=20 Cheers, Stephen Rothwell --Sig_/NYRY2U39Yzj5UUJxYYd_bFw Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmQaJCwACgkQAVBC80lX 0GyugQgAjVQo6K+XRsLVeENpXPfMUPdmXV96GbYUczY5KS5ynkqDA9tLIYi+NhUJ i0YEgg2Y4F5igYRrb7dWOzh64QMska/HFp15yPLtHIwshPCMwrnGB5vS7R90p86W qnddPE2WPli7dDR0vzib6ucT7FdjcDORcTG6pktffLbpVTLd9x5lvlpN0bvZdaYB TXvVrV9APwKLsYyGYYgRO6a/RXtkIk/g44Ar7VCKn/D4NNfsWKTWLlPHVgVi7k3y xN3vkPvqvzUDHJeUhLhXZO2ZY76suw2vhcpxAmY5q0QmwE0fsbdcO7dGhgL/Q/B5 u1dUmNenSruenwmWPP75kdWC+J0rKQ== =mUe0 -----END PGP SIGNATURE----- --Sig_/NYRY2U39Yzj5UUJxYYd_bFw--