This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] fix build failure with Python 3.7

From: Pedro Alves <palves at redhat dot com>
To: Paul dot Koning at dell dot com
Cc: sergiodj at redhat dot com, gdb-patches at sourceware dot org
Date: Fri, 1 Jun 2018 14:37:53 +0100
Subject: Re: [PATCH] fix build failure with Python 3.7
References: <96198491-96D8-42F0-9956-1C2BC9277050@dell.com> <87fu27fux2.fsf@redhat.com> <2BFDF702-C2E4-4339-ABB4-D0655063DE95@dell.com> <4e99c685-9047-bb84-8ead-ea13d4c202d3@redhat.com> <181F555B-4509-4DA2-9D10-4DF4D47D8E3F@dell.com> <1e718869-7d3d-11f3-1748-d7f34032c8d8@redhat.com> <44D6B060-1CF8-4285-9723-4EB503618855@dell.com> <5f0ab19d-02df-6462-7802-1dba8c0cf82e@redhat.com>

On 06/01/2018 02:36 PM, Pedro Alves wrote:
> On 06/01/2018 02:22 PM, Paul.Koning@dell.com wrote:
>> Ok, here is the patch in its current state.  Ok to commit?
> 
> Yes, but recall to include the rationale in the git commit log, and
> to include the link to the original Python issue in there.

Actually, should this go to the 8.1 branch too?  If so, then per
standard procedure we will indeed need a GDB bugzilla bug filed
(and then a reference added to the ChangeLog).

Thanks,
Pedro Alves

Follow-Ups:
- Re: [PATCH] fix build failure with Python 3.7
  - From: Paul.Koning

References:
- Re: [PATCH] fix build failure with Python 3.7
  - From: Pedro Alves
- Re: [PATCH] fix build failure with Python 3.7
  - From: Paul.Koning
- Re: [PATCH] fix build failure with Python 3.7
  - From: Pedro Alves
- Re: [PATCH] fix build failure with Python 3.7
  - From: Paul.Koning
- Re: [PATCH] fix build failure with Python 3.7
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]