[syslinux] [PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh

Robert Yang liezhi.yang at windriver.com
Tue Dec 23 18:13:16 PST 2014



On 12/24/2014 12:54 AM, Gene Cumm wrote:
> On Mon, Dec 22, 2014 at 8:40 PM, Ady <ady-sf at hotmail.com> wrote:
>>
>>> On Mon, 22 Dec, at 04:51:19PM, Gene Cumm wrote:
>>>>
>>>> Commit 6e832106 which originally created the shell scripts was the
>>>> first instance of this silencing.
>>>>
>>>> Aside from adding a few hundred lines of build output (which could be
>>>> beneficial), is there any reason not to remove the null redirects?
>>>
>>> There's no downside that I can see. Go for it.
>
>> The downside would be that other (much more relevant) output lines
>> could be easily missed when the log is *that* much longer. If the
>> gnu-efi commit that the Syslinux's build is pointing to is "the same as
>> always", then there shouldn't be any problem with the gnu-efi
>> submodule.
>
> Perspective.  300 lines in 4200 lines of output isn't much.
> Additionally, most issues that arise in the middle of a build's output
> are missing parallel dependencies (which are our issue and several of

I had sent 2 patches for fixing the parallel dependencies:

www.syslinux.org/archives/2014-November/022822.html
www.syslinux.org/archives/2014-November/022823.html

And they are pending.

// Robert

> these have been recently resolved) or garbage from a misbuild (ie
> doing make directly in the gnu-efi folder).
>


More information about the Syslinux mailing list