Displaying 3 results from an estimated 3 matches for "2014nov25".
Did you mean:
2008nov25
2014 Dec 22
0
check-gnu-efi.sh: print the output of build-gnu-efi.sh
...ng in certain VM environments
(OVMF, KVM, whatever). I'm not saying it has to be now, but it might be
worth testing this matter before the next pre-release (whenever it
might occur).
In particular, the *gnu-efi.sh scripts in Syslinux should be tested
with the new gnu-efi git tree (changed, 2014Nov25).
> It also levels the field such that everyone has the same version.
Using a consistent version / commit of gnu-efi makes sense. Otherwise,
the resulting behavior could be changing (or the build might fail for
some reason), according to whichever version / commit is "freely" u...
2014 Dec 22
3
[PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh
On Nov 25, 2014 12:30 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote:
> While we discuss gnu-efi. How difficult to make it using system-wide
> installed library instead of checking out and building it? Some
> systems already have gnu-efi packaged/installed. It makes sense to use
> it.
The first attempt was to do exactly that however Syslinux depended on too
2014 Dec 22
3
check-gnu-efi.sh: print the output of build-gnu-efi.sh
...in VM environments
(OVMF, KVM, whatever). I'm not saying it
has to be now, but it might be
worth
testing this matter before the next pre-release (whenever it
might occur).
In particular, the *gnu-efi.sh scripts in
Syslinux should be tested
with the new
gnu-efi git tree (changed, 2014Nov25).
> It also levels the field
such that everyone has the same version.
Using a consistent version /
commit of gnu-efi makes sense. Otherwise,
the resulting behavior could be changing (or
the build might fail for
some reason),
according to whichever version / commit is
"fr...