Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: WIP patch to build GDB with Python on MinGW
Date: Fri, 28 Jan 2011 11:21:00 -0000	[thread overview]
Message-ID: <m38vy5i8sy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20110121011433.GA2440@adacore.com> (Joel Brobecker's message of	"Thu, 20 Jan 2011 20:14:33 -0500")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> Just in case someone else would like to build their GDB with Python
Joel> support enable on MinGW. This is Work In Progress, and is only shared
Joel> here in the hopes that it might be useful.

Joel>       This opens the door for unexpected conflicts, given the filenames
Joel>       chosen by the Python implementation.  And sure enough, had a
Joel>       "cute" issue: GDB has gdb/python/python.h, and Python has
Joel>       <root>/include/Python.h.  The Windows filesystem being case
Joel>       insensitve, GCC started picking up gdb/python/python.h when
Joel>       we meant to include Python.h.

Joel>       I fixed that by renaming python.h into gdb-python.h.

Gross and unfortunate, but I don't see another solution.

It is ok with me if you want to check in these kinds of changes even if
they are not complete.

Tom


      parent reply	other threads:[~2011-01-28 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21  5:57 Joel Brobecker
2011-01-21 11:56 ` Eli Zaretskii
2011-01-21 16:24   ` Joel Brobecker
2011-01-28 11:21 ` Tom Tromey [this message]

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=m38vy5i8sy.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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