On Mon, Jul 8, 2013 at 11:42 AM, Alexander Ivchenko wrote:
>> It sounds like it is better to fix the system headers instead. Via a
>> fixincludes for older headers and have the android folks fix them for
>> newer releases.
>
> Would that count for verifing? :)
:) Indeed. I confess I didn't look
2013/7/8 Bruce Korb :
> Hi,
>
> On Mon, Jul 8, 2013 at 5:05 AM, Alexander Ivchenko wrote:
>> Hi Bruce,
>>
>> That was my original letter:
>>>Hi,
>>>
>>>Could you please take a look at the attached fixinclude patch
>>>that addresses the problem:
>>>
>>>" We have test fail for gcc.dg/cpp/trad/inclu
Hi,
On Mon, Jul 8, 2013 at 5:05 AM, Alexander Ivchenko wrote:
> Hi Bruce,
>
> That was my original letter:
>>Hi,
>>
>>Could you please take a look at the attached fixinclude patch
>>that addresses the problem:
>>
>>" We have test fail for gcc.dg/cpp/trad/include.c on Android. The
>>reason for th
Hi Bruce,
That was my original letter:
>Hi,
>
>Could you please take a look at the attached fixinclude patch
>that addresses the problem:
>
>" We have test fail for gcc.dg/cpp/trad/include.c on Android. The
>reason for that is that
>-ftraditional-cpp is not expected to work on Android due to vari
Alexander Ivchenko Mon, 29 Apr 2013 23:24:55 -0700
2013/4/29 Mike Stump :
On Jan 9, 2013, at 7:14 AM, Alexander Ivchenko wrote:
We have test fail for gcc.dg/cpp/trad/include.c on Android. The
reason for that is that
-ftraditional-cpp is not expected to work on Android due to variadic
macro (l
