From: Dragovorn <Dragovorn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: ovmf
Date: Sun, 01 Nov 2020 05:12:05 +0100 [thread overview]
Message-ID: <20201101041205.LzVKWLVI7tvUgmANsGsNATEAtVQOOHNcQCcdg-noDO8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17225@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
New comment by Dragovorn on void-packages repository
https://github.com/void-linux/void-packages/pull/17225#issuecomment-720023772
Comment:
Hello, I am encountering an issue when trying to build this package using `./xbps-src pkg ovmf-x64`, bear with me as I'm relatively new to using Void (and at most intermediate with Linux itself). I am encountering this error on build:
```
=> ERROR: edk2-202005_1: vinstall: cannot find 'Build/OvmfX64NoSb/RELEASE_GCC5/FV/OVMF_CODE.fd'...
=> ERROR: edk2-202005_1: do_install: 'return 1' exited with 1
=> ERROR: in _noglob_helper() at common/environment/setup/install.sh:12
=> ERROR: in do_install() at srcpkgs/edk2/template:133
```
Upon investigation into `masterdir/builddir/edk2-202005/edk2-edk2-stable202005/Build/OvmfX64NoSb/RELEASE_GCC5/FV` I find that it is empty with only a `Ffs` directory present.
next prev parent reply other threads:[~2020-11-01 4:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17225@inbox.vuxu.org>
2020-01-22 5:05 ` voidlinux-github
2020-01-22 5:14 ` voidlinux-github
2020-01-22 19:36 ` voidlinux-github
2020-02-27 21:45 ` Francesco149
2020-04-22 1:09 ` anjandev
2020-04-22 1:10 ` anjandev
2020-04-22 3:41 ` q66
2020-07-04 22:43 ` anjandev
2020-07-04 22:56 ` anjandev
2020-07-04 22:57 ` anjandev
2020-11-01 4:12 ` Dragovorn [this message]
2020-11-02 4:14 ` anjandev
2020-12-10 14:24 ` rinpatch
2020-12-15 16:01 ` Dragovorn
2021-02-16 6:17 ` ericonr
2021-02-16 6:17 ` [PR PATCH] [Closed]: " ericonr
2021-02-17 9:47 ` rinpatch
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=20201101041205.LzVKWLVI7tvUgmANsGsNATEAtVQOOHNcQCcdg-noDO8@z \
--to=dragovorn@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).