Displaying 3 results from an estimated 3 matches for "misbuild".
2014 Dec 23
1
[PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh
...lem 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
these have been recently resolved) or garbage from a misbuild (ie
doing make directly in the gnu-efi folder).
--
-Gene
2014 Dec 23
0
[PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh
> 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
2014 Dec 22
2
[PATCH] check-gnu-efi.sh: print the output of build-gnu-efi.sh
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.
--
Matt Fleming, Intel Open