From: "Michal Suchánek" <msuchanek@suse.de>
To: Yonghong Song <yhs@fb.com>
Cc: linux-kernel@vger.kernel.org, Martin KaFai Lau <kafai@fb.com>,
"David S. Miller" <davem@davemloft.net>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Song Liu <songliubraving@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: linux-next failing build due to missing cubictcp_state symbol
Date: Fri, 23 Apr 2021 19:55:28 +0200 [thread overview]
Message-ID: <20210423175528.GF6564@kitsune.suse.cz> (raw)
In-Reply-To: <316e86f9-35cc-36b0-1594-00a09631c736@fb.com>
On Fri, Apr 23, 2021 at 07:41:29AM -0700, Yonghong Song wrote:
>
>
> On 4/23/21 6:05 AM, Michal Suchánek wrote:
> > Hello,
> >
> > I see this build error in linux-next (config attached).
> >
> > [ 4939s] LD vmlinux
> > [ 4959s] BTFIDS vmlinux
> > [ 4959s] FAILED unresolved symbol cubictcp_state
> > [ 4960s] make[1]: ***
> > [/home/abuild/rpmbuild/BUILD/kernel-vanilla-5.12~rc8.next.20210422/linux-5.12-rc8-next-20210422/Makefile:1277:
> > vmlinux] Error 255
> > [ 4960s] make: *** [../Makefile:222: __sub-make] Error 2
>
> Looks like you have DYNAMIC_FTRACE config option enabled already.
> Could you try a later version of pahole?
Is this requireent new?
I have pahole 1.20, and master does build without problems.
If newer version is needed can a check be added?
Thanks
Michal
next prev parent reply other threads:[~2021-04-23 17:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 13:05 linux-next failing build due to missing cubictcp_state symbol Michal Suchánek
2021-04-23 14:41 ` Yonghong Song
2021-04-23 17:55 ` Michal Suchánek [this message]
2021-04-25 11:15 ` Michal Suchánek
2021-04-26 11:32 ` Michal Suchánek
2021-04-26 12:12 ` Michal Suchánek
2021-04-26 12:14 ` Michal Suchánek
2021-04-26 15:41 ` Yonghong Song
2021-04-26 16:03 ` Jiri Olsa
2021-04-26 19:16 ` Jiri Olsa
2021-04-27 12:12 ` Michal Suchánek
2021-04-30 17:47 ` Michal Suchánek
2021-04-30 18:26 ` Michal Suchánek
2021-05-01 6:45 ` Jiri Slaby
2021-05-01 10:54 ` Michal Suchánek
2021-05-03 6:11 ` Jiri Slaby
2021-05-03 7:13 ` Michal Suchánek
2021-05-03 7:59 ` Jiri Slaby
2021-05-03 8:59 ` Jiri Slaby
2021-05-03 10:08 ` Jiri Olsa
2021-05-03 16:46 ` Michal Suchánek
2021-05-03 16:58 ` Michal Suchánek
2021-05-04 6:41 ` Jiri Slaby
2021-05-06 5:31 ` Martin KaFai Lau
2021-05-06 13:16 ` Jiri Olsa
2021-05-07 7:10 ` Florian Weimer
2021-05-05 13:56 ` Michal Suchánek
2021-05-06 4:31 ` Jiri Slaby
2021-05-06 5:20 ` Martin KaFai Lau
2021-05-06 5:54 ` Jiri Slaby
2021-05-06 8:19 ` Michal Suchánek
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=20210423175528.GF6564@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).