Re: [Lldb-commits] [PATCH] D19092: Fix Android build after r266267

labath added a subscriber: labath. labath added a comment. Judging by the cryptic error message, and the fact that a global variable should not cause an issue, i suspect stdout was a macro in this case... http://reviews.llvm.org/D19092 ___

Re: [Lldb-commits] [PATCH] D19092: Fix Android build after r266267

> On Apr 14, 2016, at 10:56 AM, Oleksiy Vyalov via lldb-commits > wrote: > > ovyalov added a comment. > > In http://reviews.llvm.org/D19092#401450, @jingham wrote: > >> Why is this necessary? stdout is a local variable defined in this scope. >> Why would the

Re: [Lldb-commits] [PATCH] D19092: Fix Android build after r266267

ovyalov added a comment. In http://reviews.llvm.org/D19092#401450, @jingham wrote: > Why is this necessary? stdout is a local variable defined in this scope. > Why would the android g++ have problems with this? > > Anyway, if you have to avoid using stdout as a name, maybe name it std_out as

Re: [Lldb-commits] [PATCH] D19092: Fix Android build after r266267

jingham added a subscriber: jingham. jingham added a comment. Why is this necessary? stdout is a local variable defined in this scope. Why would the android g++ have problems with this? Anyway, if you have to avoid using stdout as a name, maybe name it std_out as that better reflects its

Re: [Lldb-commits] [PATCH] D19092: Fix Android build after r266267

ovyalov added a comment. Submitted as http://reviews.llvm.org/rL266274 http://reviews.llvm.org/D19092 ___ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits