From: Ignat Korchagin <ignat@cloudflare.com>
To: jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, brendanhiggins@google.com,
masahiroy@kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: kernel-team@cloudflare.com, Ignat Korchagin <ignat@cloudflare.com>
Subject: [PATCH v4 0/3] um: allow static linking for non-glibc libc implementations
Date: Sun, 19 Jul 2020 22:02:19 +0100 [thread overview]
Message-ID: <20200719210222.2811-1-ignat@cloudflare.com> (raw)
Changes from v3:
* restored FORBID_STATIC_LINK and renamed it to MAY_HAVE_RUNTIME_DEPS, so we
don't have to maintain a static list of options, which may produce runtime
dependencies
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-ignat@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 | 6 +++---
arch/um/drivers/Kconfig | 6 +++---
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, 26 insertions(+), 20 deletions(-)
--
2.20.1
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
WARNING: multiple messages have this Message-ID (diff)
From: Ignat Korchagin <ignat@cloudflare.com>
To: jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, brendanhiggins@google.com,
masahiroy@kernel.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Ignat Korchagin <ignat@cloudflare.com>, kernel-team@cloudflare.com
Subject: [PATCH v4 0/3] um: allow static linking for non-glibc libc implementations
Date: Sun, 19 Jul 2020 22:02:19 +0100 [thread overview]
Message-ID: <20200719210222.2811-1-ignat@cloudflare.com> (raw)
Changes from v3:
* restored FORBID_STATIC_LINK and renamed it to MAY_HAVE_RUNTIME_DEPS, so we
don't have to maintain a static list of options, which may produce runtime
dependencies
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-ignat@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 | 6 +++---
arch/um/drivers/Kconfig | 6 +++---
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, 26 insertions(+), 20 deletions(-)
--
2.20.1
next reply other threads:[~2020-07-19 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 21:02 Ignat Korchagin [this message]
2020-07-19 21:02 ` [PATCH v4 0/3] um: allow static linking for non-glibc libc implementations Ignat Korchagin
2020-07-19 21:02 ` [PATCH v4 1/3] um/kconfig: introduce CC_CAN_LINK_STATIC_NO_RUNTIME_DEPS Ignat Korchagin
2020-07-19 21:02 ` Ignat Korchagin
2020-07-19 21:02 ` [PATCH v4 2/3] um: some fixes to build UML with musl Ignat Korchagin
2020-07-19 21:02 ` Ignat Korchagin
2020-07-19 21:02 ` [PATCH v4 3/3] um: allow static linking for non-glibc implementations Ignat Korchagin
2020-07-19 21:02 ` Ignat Korchagin
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=20200719210222.2811-1-ignat@cloudflare.com \
--to=ignat@cloudflare.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=brendanhiggins@google.com \
--cc=jdike@addtoit.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=richard@nod.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.