[PATCH v1] uml: make CONFIG_STATIC_LINK actually static

From: Brendan Higgins
Date: Tue Dec 10 2019 - 16:21:38 EST


Currently, CONFIG_STATIC_LINK can be enabled with options which cannot
be statically linked, namely UML_NET_VECTOR, UML_NET_VDE, and
UML_NET_PCAP; this is because glibc tries to load NSS which does not
support being statically linked. So make CONFIG_STATIC_LINK depend on
!UML_NET_VECTOR && !UML_NET_VDE && !UML_NET_PCAP.

Link: https://lore.kernel.org/lkml/f658f317-be54-ed75-8296-c373c2dcc697@xxxxxxxxxxxxxxxxxx/#t
Signed-off-by: Brendan Higgins <brendanhiggins@xxxxxxxxxx>
---
arch/um/Kconfig | 4 ++++
1 file changed, 4 insertions(+)

diff --git a/arch/um/Kconfig b/arch/um/Kconfig
index 2a6d04fcb3e91..1ddc8745123f2 100644
--- a/arch/um/Kconfig
+++ b/arch/um/Kconfig
@@ -63,6 +63,7 @@ source "arch/$(HEADER_ARCH)/um/Kconfig"

config STATIC_LINK
bool "Force a static link"
+ depends on !UML_NET_VECTOR && !UML_NET_VDE && !UML_NET_PCAP
default n
help
This option gives you the ability to force a static link of UML.
@@ -72,6 +73,9 @@ config STATIC_LINK
Additionally, this option enables using higher memory spaces (up to
2.75G) for UML.

+ NOTE: This option is incompatible with some networking features which
+ depend on features that require being dynamically loaded (like NSS).
+
config LD_SCRIPT_STATIC
bool
default y
--
2.24.0.525.g8f36a354ae-goog