Syslinux - Nov 2014 - [PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh

> _ The gnu-efi git repository is currently partially unavailable. Trying 
> to retrieve older commits (as the one used in the official release of 
> Syslinux 6.03 stable) might succeed, but, at this moment, trying to 
> retrieve the official gnu-efi master head will fail.
 
Update: after several days, the gnu-efi master head is now available 
again.

I do not discard the possibility of seeing it disappearing again in the 
future, as this seems to be a misunderstanding / mismanagement of the 
git repo / git commands.

Regards,
Ady.

Hi

On Mon, Nov 24, 2014 at 8:20 PM, Ady <ady-sf at hotmail.com>
wrote:
>
>> _ The gnu-efi git repository is currently partially unavailable. Trying
>> to retrieve older commits (as the one used in the official release of
>> Syslinux 6.03 stable) might succeed, but, at this moment, trying to
>> retrieve the official gnu-efi master head will fail.
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.
> Update: after several days, the gnu-efi master head is now available
> again.
>
> I do not discard the possibility of seeing it disappearing again in the
> future, as this seems to be a misunderstanding / mismanagement of the
> git repo / git commands.
>
> Regards,
> Ady.
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux

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
many bleeding edge commits of gnu-efi to make it viable.  It also levels
the field such that everyone has the same version.

The only viable alternatives I can think of are:

1) Use our own repo.
2) Put a Makefile variable in to indicate to use system then check if
sufficient else fail the entire build.

Bear in mind this also complicates debugging.

--Gene