From: Andrew STUBBS <andrew.stubbs@st.com>
To: Steve Folly <gdb-list@spfweb.co.uk>
Cc: GDB List <gdb@sources.redhat.com>
Subject: Re: Can't build gdb for mingw32 if not native? :-(
Date: Wed, 28 Sep 2005 11:52:00 -0000 [thread overview]
Message-ID: <433A7285.9060207@st.com> (raw)
In-Reply-To: <EBA35A1E-5131-4A5E-8547-515BE0C26D94@spfweb.co.uk>
Steve Folly wrote:
>
> On 27 Sep 2005, at 22:18, Daniel Jacobowitz wrote:
>
>> On Tue, Sep 27, 2005 at 10:12:40PM +0100, Steve Folly wrote:
>>
>>> Hi,
>>>
>>> I'm trying to build gdb 6.3 on host powerpc-apple-darwin8.2.0 for
>>> target i386-pc-mingw32msvc.
>>>
>>
>> GDB 6.3 doesn't support the mingw32 target. In fact it doesn't support
>> mingw32 as a host either. Later versions will support it as a host but
>> not target.
>
>
> The configure script in the gdb-6.3.tar.gz I downloaded seems to?
The top level configure script may do, but as Daniel says the GDB
sources do not.
Look at www.mingw.org for GDB MinGW patches (GDB 6.3-1 last time I
looked). These will get it to compile for MinGW, but, even if they can
be made to cross compile, Daniel's point about remote debugging still
stands. I can see why you wouldn't want to use Windows as a build
platform, but I suggest that, unless you have a good reason not to, you
debug the programs natively using the native MinGW GDB. You can probably
download a binary from their website along with the rest of MinGW/MSYS.
Alternatively, the GDB in Cygwin (www.cygwin.com) is capable of
debugging MinGW programs. Cygwin also has support for compiling them
with 'gcc -mno-cygwin'. Note that the standard Cygwin install does not
include developer tools, but the installation tool is quite easy to use.
HTH
Andrew
next prev parent reply other threads:[~2005-09-28 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 21:11 Steve Folly
2005-09-27 21:12 ` Steve Folly
2005-09-27 21:18 ` Daniel Jacobowitz
2005-09-27 21:54 ` Steve Folly
2005-09-27 22:26 ` Daniel Jacobowitz
2005-09-28 11:52 ` Andrew STUBBS [this message]
2005-09-28 20:08 ` Steve Folly
2005-09-28 21:21 ` Eli Zaretskii
2005-09-29 0:41 ` Christopher Faylor
2005-09-29 9:01 ` Dave Murphy
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=433A7285.9060207@st.com \
--to=andrew.stubbs@st.com \
--cc=gdb-list@spfweb.co.uk \
--cc=gdb@sources.redhat.com \
/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