This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Fix compilation warnings triggered by Python's pyerrors.h
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 15 Mar 2013 16:39:29 +0200
- Subject: Re: Fix compilation warnings triggered by Python's pyerrors.h
- References: <83sj3zi216.fsf@gnu.org> <87k3p97u3u.fsf@fleche.redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Thu, 14 Mar 2013 11:45:57 -0600
>
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>
> Eli> Suggested work-around: Define HAVE_SNPRINTF in defs.h:
>
> Why defs.h and not python-internal.h?
Because I didn't know that all includes of pyerrors.h go through
python-internal.h ;-)
> I think that, if it works, it is better to try to contain the weirdness
> to the Python code.
I agree. I will make sure it works and commit a modified patch.
Thanks.