* [PR PATCH] qemu-user-static: statically link binaries.
@ 2020-05-23 10:35 thallian
2020-05-24 7:46 ` [PR PATCH] [Merged]: " Hoshpak
0 siblings, 1 reply; 2+ messages in thread
From: thallian @ 2020-05-23 10:35 UTC (permalink / raw)
To: ml
[-- 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() {
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PR PATCH] [Merged]: qemu-user-static: statically link binaries.
2020-05-23 10:35 [PR PATCH] qemu-user-static: statically link binaries thallian
@ 2020-05-24 7:46 ` Hoshpak
0 siblings, 0 replies; 2+ messages in thread
From: Hoshpak @ 2020-05-24 7:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
There's a merged pull request on the void-packages repository
qemu-user-static: statically link binaries.
https://github.com/void-linux/void-packages/pull/22225
Description:
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-05-24 7:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-23 10:35 [PR PATCH] qemu-user-static: statically link binaries thallian
2020-05-24 7:46 ` [PR PATCH] [Merged]: " Hoshpak
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).