[PATCH] [LNT] Tolerate "clang -v" output without leading spaces

[Jingyue Wu]

Sorry for the buzz. Looks like I am working on an old version. This issue
has likely been fixed already.

Thanks,
Jingyue

On Mon Aug 11 2014 at 2:44:03 PM Chris Matthews <chris4000 at gmail.com> wrote:

> I had assumed those were removed in error, and has been fixed?
>
> > On Aug 11, 2014, at 2:11 PM, Yi Kong <kongy.dev at gmail.com> wrote:
> >
> > Leading spaces are added back as of r215044.
> >
> > -Yi
> >
> > On 11 August 2014 21:55, Jingyue Wu <jingyue at google.com> wrote:
> >> + Daniel and Chris
> >>
> >>
> >> On Mon Aug 11 2014 at 1:36:14 PM Jingyue Wu <jingyue at google.com> wrote:
> >>>
> >>> The output of "clang -v -E -x c /dev/null -###" on the trunk doesn't
> have
> >>> the leading spaces as previous versions.
> >>>
> >>> "/home/jingyue/Work/llvm/install-git/bin/clang" "-cc1" "-triple"
> >>> "x86_64-unknown-linux-gnu" "-E" ...
> >>>
> >>> This patch makes the leading space optional; otherwise, compiler.py
> will
> >>> not be able to find the cc1 binary.
> >>>
> >>> Jingyue
> >>
> >>
> >> _______________________________________________
> >> llvm-commits mailing list
> >> llvm-commits at cs.uiuc.edu
> >> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
> >>
> > _______________________________________________
> > llvm-commits mailing list
> > llvm-commits at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140811/cd9baa6e/attachment.html>