From: thallian <thallian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] qemu-user-static: statically link binaries.
Date: Sat, 23 May 2020 12:35:20 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22225@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
There is a new pull request by thallian against master on the void-packages repository
https://github.com/thallian/void-packages master
https://github.com/void-linux/void-packages/pull/22225
qemu-user-static: statically link binaries.
With the addition of '---static' to the configure stage, the resulting binaries are actually statically linked.
When running mkrootfs from void-mklive for an aarch64 target I ran into the exact problem described here: https://github.com/void-linux/void-mklive/issues/125
After recompiling the qemu-user-static package with this fix it started to work flawlessly and ldd also says that it is not a dynamic executable (which wasn't the case before).
I tested this on a x86_64-musl voidlinux installation.
A patch file from https://github.com/void-linux/void-packages/pull/22225.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-22225.patch --]
[-- Type: text/x-diff, Size: 1206 bytes --]
From b084e96f539ba166ab364748acd55a2013276951 Mon Sep 17 00:00:00 2001
From: Sebastian Hugentobler <sebastian@vanwa.ch>
Date: Sat, 23 May 2020 12:17:32 +0200
Subject: [PATCH] qemu-user-static: statically link binaries.
With the addition of '---static' to the configure stage, the
resulting binaries are actually statically linked.
---
srcpkgs/qemu-user-static/template | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/qemu-user-static/template b/srcpkgs/qemu-user-static/template
index af3dd9161fc..538bbebf8ab 100644
--- a/srcpkgs/qemu-user-static/template
+++ b/srcpkgs/qemu-user-static/template
@@ -1,7 +1,7 @@
# Template file for 'qemu-user-static'
pkgname=qemu-user-static
version=5.0.0
-revision=1
+revision=2
wrksrc="qemu-${version}"
hostmakedepends="pkg-config automake python3"
makedepends="dtc-devel libglib-static pixman-devel libuuid-devel"
@@ -87,7 +87,8 @@ do_configure() {
./configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/libexec \
--disable-kvm --disable-vnc-png \
--disable-virtfs --disable-fdt --disable-seccomp \
- --enable-linux-user --disable-system
+ --enable-linux-user --disable-system \
+ --static
}
do_build() {
next reply other threads:[~2020-05-23 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 10:35 thallian [this message]
2020-05-24 7:46 ` [PR PATCH] [Merged]: " Hoshpak
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22225@inbox.vuxu.org \
--to=thallian@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).