From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu(-user-static): update to 7.2.0.
Date: Thu, 22 Dec 2022 01:42:14 +0100 [thread overview]
Message-ID: <20221222004214.YVts7mh4hquCnz7kFjrMwUGYCbDqMez8RyNR2IpOOZk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41138@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/41138#issuecomment-1362056086
Comment:
The glib thing is a warning not an error, you can safely ignore it.
For the i686 issue:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908331
You can use `--disable-pie` in qemu-user-static (this is used by Debian and Fedora).
https://salsa.debian.org/qemu-team/qemu/-/blob/master/debian/rules#L342-359
The aarch64 and armv7l issues are probably caused by this:
https://github.com/void-linux/void-packages/commit/b2d670be60b883192d12f79077fa79dff5395554
Which wasn't an issue before since the glibc cross compilers weren't rebuilt.
I made a PR for it here: https://github.com/void-linux/void-packages/pull/41229
next prev parent reply other threads:[~2022-12-22 0:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 5:47 [PR PATCH] " unspecd
2022-12-18 15:51 ` [PR PATCH] [Updated] " unspecd
2022-12-19 6:43 ` unspecd
2022-12-19 6:46 ` unspecd
2022-12-21 11:39 ` unspecd
2022-12-21 20:25 ` oreo639
2022-12-22 0:41 ` oreo639
2022-12-22 0:42 ` oreo639 [this message]
2022-12-22 9:28 ` [PR PATCH] [Updated] " unspecd
2022-12-22 11:55 ` unspecd
2023-01-21 1:10 ` oreo639
2023-01-22 7:06 ` [PR PATCH] [Updated] " unspecd
2023-01-22 9:37 ` unspecd
2023-02-17 13:27 ` [PR PATCH] [Updated] " unspecd
2023-02-17 13:28 ` unspecd
2023-04-16 9:39 ` [PR PATCH] [Updated] " unspecd
2023-04-16 9:39 ` unspecd
2023-04-22 23:33 ` [PR PATCH] [Updated] qemu(-user-static): update to 7.2.1 unspecd
2023-05-18 11:46 ` qemu(-user-static): update to 8.0.0 AnErrupTion
2023-08-01 8:08 ` [PR PATCH] [Closed]: " unspecd
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=20221222004214.YVts7mh4hquCnz7kFjrMwUGYCbDqMez8RyNR2IpOOZk@z \
--to=oreo639@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).