From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Masahiro Yamada <masahiroy@kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
"David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: linux-next 20200506 - build failure with net/bpfilter/bpfilter_umh
Date: Fri, 08 May 2020 00:39:16 -0400 [thread overview]
Message-ID: <251580.1588912756@turing-police> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
My kernel build came to a screeching halt with:
CHECK net/bpfilter/bpfilter_kern.c
CC [M] net/bpfilter/bpfilter_kern.o
CC [U] net/bpfilter/main.o
LD [U] net/bpfilter/bpfilter_umh
/usr/bin/ld: cannot find -lc
collect2: error: ld returned 1 exit status
make[2]: *** [scripts/Makefile.userprogs:36: net/bpfilter/bpfilter_umh] Error 1
make[1]: *** [scripts/Makefile.build:494: net/bpfilter] Error 2
make: *** [Makefile:1726: net] Error 2
The culprit is this commit:
commit 0592c3c367c4c823f2a939968e72d39360fce1f4
Author: Masahiro Yamada <masahiroy@kernel.org>
Date: Wed Apr 29 12:45:15 2020 +0900
bpfilter: use 'userprogs' syntax to build bpfilter_umh
and specifically, this line:
+userldflags += -static
At least on Fedora, this dies an ugly death unless you have the glibc-static RPM
installed (which is *not* part of the glibc-devel RPM). Not sure how to fix this, or
give a heads-up that there's a new requirement that might break the build.
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2020-05-08 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 4:39 Valdis Klētnieks [this message]
2020-05-09 3:45 ` linux-next 20200506 - build failure with net/bpfilter/bpfilter_umh Masahiro Yamada
2020-05-09 4:39 ` Valdis Klētnieks
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=251580.1588912756@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.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