> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre wrote:
>
> On Thu, 4 Jun 2015, Jim Wilson wrote:
>
>> The normal toolchain process is that patches get added to our releases
>> only if they are already upstream. Our releases are FSF releases plus
>> patches backported from mainline, with no local c
On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
>> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre wrote:
>>
>> On Thu, 4 Jun 2015, Jim Wilson wrote:
>>
>>> The normal toolchain process is that patches get added to our releases
>>> only if they are already upstream. Our releases are FSF releases plus
>>>
On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>
> On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
> >> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre
> >> wrote:
> >>
> >> On Thu, 4 Jun 2015, Jim Wilson wrote:
> >>
> >>> The normal toolchain process is that patches get added to our releases
> >>> on
On 18-06-2015 11:26, Nicolas Pitre wrote:
> On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>>
>>
>> On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
On Jun 17, 2015, at 3:15 AM, Nicolas Pitre
wrote:
On Thu, 4 Jun 2015, Jim Wilson wrote:
> The normal toolchain process i
On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>
> On 18-06-2015 11:26, Nicolas Pitre wrote:
> > On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
> >
> >>
> >>
> >> On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre
> wrote:
>
> On Thu,
It seems the prebuilt windows releases of GDB do not enable Python.
Are there plans to release a python-enabled-gdb in the windows builds?
If not, what are the roadblocks to this?
Thanks
Example:
$ ./aarch64-linux-gnu-gdb.exe
GNU gdb (Linaro GDB 2015.02-3) 7.8-2014.09-1-git
Copyright (C) 2014
