From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFA] Build failure fix: Python troubles on non-python targets...
Date: Thu, 28 May 2009 16:37:00 -0000 [thread overview]
Message-ID: <m363fltc9v.fsf@fleche.redhat.com> (raw)
In-Reply-To: <001c01c9dfb0$74dfec40$5e9fc4c0$@u-strasbg.fr> (Pierre Muller's message of "Thu\, 28 May 2009 18\:22\:11 +0200")
>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
Pierre> Here is what I get if I move it down:
[...]
Pierre> ../../purecvs/gdb/python/python-prettyprint.c:598: error: conflicting types
Pierre> for
Pierre> 'apply_val_pretty_printer'
Evidently I haven't done a python-less build in a while :-(
Anyway, this is exactly the kind of error that the inclusion of
python.h is supposed to detect. So at least that is working ok :)
Go ahead and commit your patch.
Paul can then check in his additional fix.
Tom
next prev parent reply other threads:[~2009-05-28 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 10:03 Pierre Muller
2009-05-28 14:56 ` Paul Pluzhnikov
2009-05-28 15:38 ` Tom Tromey
2009-05-28 16:22 ` Pierre Muller
2009-05-28 16:23 ` Paul Pluzhnikov
2009-05-28 16:37 ` Tom Tromey [this message]
2009-05-28 16:31 ` Paul Pluzhnikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m363fltc9v.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox