Displaying 3 results from an estimated 3 matches for "2014oct06".
Did you mean:
2014oct
2014 Dec 22
0
check-gnu-efi.sh: print the output of build-gnu-efi.sh
> Syslinux depended on too many bleeding edge commits of gnu-efi to
> make it viable.
That _seems_ to be no longer accurate. The official 6.03 release
(2014Oct06) was built based on the gnu-efi commit:
ab54e2b40e914d0ca01dc3d44c8d4eb8517bf999 from 2014Feb13.
At the time Syslinux 6.03 was released, the build was no longer using a
"bleeding edge" commit of gnu-efi (it was several months old and dozens
of commits old). By the time I am writing thi...
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
...x] check-gnu-efi.sh: print the output of build-gnu-efi.sh
To: syslinux at zytor.com
Date: Monday, December 22, 2014, 9:29 AM
>
Syslinux depended on too many bleeding edge commits of
gnu-efi to
> make it viable.
That _seems_ to be no longer
accurate. The official 6.03 release
(2014Oct06) was built based on the gnu-efi
commit:
ab54e2b40e914d0ca01dc3d44c8d4eb8517bf999 from 2014Feb13.
At the time Syslinux 6.03 was released, the
build was no longer using a
"bleeding
edge" commit of gnu-efi (it was several months old and
dozens
of commits old). By the time I am
w...