On Fri, Oct 28, 2016 at 11:12 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote: > From: Emil Velikov <emil.veli...@collabora.com> > > Otherwise we get annoying messages like the following when xxd is > missing. > > /bin/sh: line 2: -i: command not found
That error is better than what we'd get after this patch. "cat ... | >> ..." looks like it generates zsh: parse error near `\n' and bash: syntax error near unexpected token `newline' > > Cc: mesa-sta...@lists.freedesktop.org > Cc: Lionel Landwerlin <lionel.g.landwer...@intel.com> > Signed-off-by: Emil Velikov <emil.veli...@collabora.com> > --- > I'm wondering if we shouldn't give some form or warning/error message > when xxd is missing ? Just fix the real problem of checking for xxd. It should be the same as what we do with bison and flex. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
