From: gspe <gspe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu: datadir is not set, uefi support is broken
Date: Wed, 20 Jan 2021 18:55:29 +0100 [thread overview]
Message-ID: <20210120175529.ip-zb74HwtcWpVd0CfbDcg__wnpGirifIB1OT8sgd2s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
New comment by gspe on void-packages repository
https://github.com/void-linux/void-packages/issues/27965#issuecomment-763825068
Comment:
@ericonr I've tried to make a PR for qemu but I have a problem: building the package fails tests.
I have updated my void-packages repo and tried to build the original qemu in void-packages without any changes and it also fails test.
Regarding the meson build style I have read some documentation and according with the changelog https://wiki.qemu.org/ChangeLog/5.2#Build_Information the switch to meson is not complete at the moment:
> The build system is now partly based on Meson. However, building is still done with configure and make as in previous versions of QEMU.
indeed some building options are still not present in `meson_options.txt` file.
next prev parent reply other threads:[~2021-01-20 17:55 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 10:40 [ISSUE] " gspe
2021-01-19 21:22 ` ericonr
2021-01-19 22:51 ` gspe
2021-01-19 22:55 ` ericonr
2021-01-20 17:55 ` gspe [this message]
2021-01-20 17:55 ` gspe
2021-01-21 1:41 ` ericonr
2021-01-21 1:42 ` ericonr
2021-01-21 21:02 ` gspe
2021-01-21 21:10 ` ericonr
2021-01-21 21:15 ` gspe
2021-01-21 21:19 ` ericonr
2021-01-21 21:21 ` gspe
2021-01-21 21:22 ` gspe
2021-01-21 21:23 ` gspe
2021-01-21 21:24 ` gspe
2021-01-21 21:28 ` ericonr
2021-01-24 15:14 ` ackalker
2021-01-24 15:17 ` ackalker
2021-01-24 15:19 ` ackalker
2021-01-24 15:21 ` ackalker
2021-01-24 15:28 ` ackalker
2021-01-24 15:42 ` ackalker
2021-01-24 15:46 ` ackalker
2021-01-24 15:48 ` ackalker
2021-01-24 17:39 ` ackalker
2021-01-24 17:39 ` ackalker
2021-01-24 17:45 ` ackalker
2021-01-24 17:46 ` ackalker
2021-01-24 17:47 ` ackalker
2021-01-24 17:48 ` ackalker
2021-01-24 17:51 ` ackalker
2021-01-24 17:52 ` ackalker
2021-01-24 17:52 ` ackalker
2021-01-24 17:53 ` ackalker
2021-01-24 17:54 ` ackalker
2021-01-24 17:56 ` ackalker
2021-01-24 17:56 ` ackalker
2021-01-24 17:58 ` ackalker
2021-01-24 18:01 ` ackalker
2021-01-24 18:02 ` ackalker
2021-01-24 18:10 ` ackalker
2021-01-25 2:21 ` ackalker
2021-01-25 2:23 ` ackalker
2021-01-25 2:23 ` ackalker
2021-01-25 2:40 ` ackalker
2021-01-25 2:43 ` ackalker
2021-01-25 2:45 ` ackalker
2021-01-25 2:49 ` ackalker
2021-01-25 2:51 ` ackalker
2021-01-25 2:52 ` ackalker
2021-01-25 2:55 ` ackalker
2021-01-25 2:59 ` ackalker
2021-01-25 3:02 ` ackalker
2021-01-25 3:04 ` ackalker
2021-01-25 3:04 ` ackalker
2021-01-25 3:05 ` ackalker
2021-01-25 3:07 ` ackalker
2021-01-25 3:07 ` ackalker
2021-01-25 3:10 ` ackalker
2021-01-25 7:04 ` ackalker
2021-01-25 7:08 ` ackalker
2021-01-25 7:09 ` ackalker
2021-01-25 7:10 ` ackalker
2021-01-26 2:57 ` ackalker
2021-01-26 2:57 ` ackalker
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=20210120175529.ip-zb74HwtcWpVd0CfbDcg__wnpGirifIB1OT8sgd2s@z \
--to=gspe@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).