Changes from v2:
* rebased to accomodate b816b3db15f68690ee72a4a414624f8e82942b25 ("kbuild:
fix CONFIG_CC_CAN_LINK(_STATIC) for cross-compilation with Clang")
* removed unused FORBID_STATIC_LINK config option
* cc-ed Masahiro Yamada <masahi...@kernel.org> for can-link.sh approve
This is a continuation of [1]. Since I was able to produce a working UML binary
with UML_NET_VECTOR linked with musl with the changes included in the patches
here. I was compiling on Arch Linux, so hopefully all the latest versions of
the compiler, libraries and binutils.
I also tested allyesconfig with both musl and glibc. The compilation succeeds
with both, however both binaries (glibc one being dynamically linked) segfault
on start. This is probably of some incompatible config option/module being
included and not related to musl/glibc.
[1]:
https://patchwork.ozlabs.org/project/linux-um/patch/20200624212319.403689-1-ig...@cloudflare.com/
Ignat Korchagin (3):
um/kconfig: introduce CC_CAN_LINK_STATIC_NO_RUNTIME_DEPS
um: some fixes to build UML with musl
um: allow static linking for non-glibc implementations
arch/um/Kconfig | 5 +----
arch/um/drivers/Kconfig | 3 ---
arch/um/drivers/daemon_user.c | 1 +
arch/um/drivers/pcap_user.c | 12 ++++++------
arch/um/drivers/slip_user.c | 2 +-
arch/um/drivers/vector_user.c | 4 +---
arch/um/os-Linux/util.c | 2 +-
arch/x86/um/user-offsets.c | 2 +-
init/Kconfig | 6 ++++++
scripts/cc-can-link.sh | 5 +++--
10 files changed, 21 insertions(+), 21 deletions(-)
--
2.20.1
