From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=-11.0 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable 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 5FEAAC43331 for ; Mon, 11 Jan 2021 22:33:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3B9E822D06 for ; Mon, 11 Jan 2021 22:33:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389320AbhAKWdV (ORCPT ); Mon, 11 Jan 2021 17:33:21 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:27080 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387685AbhAKWdV (ORCPT ); Mon, 11 Jan 2021 17:33:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610404315; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Wnlkg0g7e1YrcYGzfxmDxEbKCTeITWcoDDln+owCI50=; b=TOGr/KA0iy7btmat781f29juhS9hVqLITo7mu4l6AKndrK9FjMGjZJ3jRr+JzwtbibmM4L lzl4QfJoDYE7fCYFBNLTCNKBhB7ye344gxfhYccScwvERJw5asJoFMXuXRtzcxwbJP4zdc a9w/pNlFgaeK+BQyxYsJb9tqjY/WSAk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-190-b6nLIsbPN4OWS0SdgOsH9g-1; Mon, 11 Jan 2021 17:31:51 -0500 X-MC-Unique: b6nLIsbPN4OWS0SdgOsH9g-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D8743DF8A4; Mon, 11 Jan 2021 22:31:48 +0000 (UTC) Received: from krava (unknown [10.40.192.185]) by smtp.corp.redhat.com (Postfix) with SMTP id B5BCB60BE2; Mon, 11 Jan 2021 22:31:45 +0000 (UTC) Date: Mon, 11 Jan 2021 23:31:44 +0100 From: Jiri Olsa To: Sedat Dilek Cc: Andrii Nakryiko , Jiri Olsa , Yonghong Song , Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko , Martin KaFai Lau , Song Liu , John Fastabend , KP Singh , Masahiro Yamada , bpf , Linux Kbuild mailing list , Tom Stellard Subject: Re: Check pahole availibity and BPF support of toolchain before starting a Linux kernel build Message-ID: <20210111223144.GA1250730@krava> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org On Mon, Jan 11, 2021 at 10:30:22PM +0100, Sedat Dilek wrote: SNIP > > > > > > Building a new Linux-kernel... > > > > > > - Sedat - > > > > > > [1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/ > > > [2] https://github.com/ClangBuiltLinux/tc-build/issues/129#issuecomment-758026878 > > > [3] https://github.com/ClangBuiltLinux/tc-build/issues/129#issuecomment-758056553 > > > > There are no significant bug fixes between pahole 1.19 and master that > > would solve this problem, so let's try to repro this. > > > > You are right pahole fom latest Git does not solve the issue. > > + info BTFIDS vmlinux > + [ != silent_ ] > + printf %-7s %s\n BTFIDS vmlinux > BTFIDS vmlinux > + ./tools/bpf/resolve_btfids/resolve_btfids vmlinux > FAILED: load BTF from vmlinux: Invalid argument hm, is there a .BTF section in vmlinux? is this working over vmlinux: $ bpftool btf dump file ./vmlinux do you have a verbose build output? I'd think pahole scream first.. jirka