From: Daniel Jacobowitz <drow@false.org>
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: Tue, 27 Sep 2005 21:18:00 -0000 [thread overview]
Message-ID: <20050927211834.GA20921@nevyn.them.org> (raw)
In-Reply-To: <6C484B02-DD81-46A9-97FB-15EEE6F0B8DC@spfweb.co.uk>
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.
> Unfortunately nothing much gets built. Probably because of the bit of
> the configure script I found that starts with the comment:
>
> # Can't build gdb for mingw32 if not native.
This line does not appear in the GDB I'm looking at. You must be using
someone's mingw32 patches.
> I'm trying to get a GNU toolset hosted on OS X and targetting Windows
> (MinGW). So far, the compiler toolset is working dandy, and having
> gdb would top it off just right.
Note, even if this worked, you'd need a remote debug agent for Windows.
There isn't one finished yet (though I have an unfinished one lying
around somewhere if I can ever find the time).
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-27 21:18 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 [this message]
2005-09-27 21:54 ` Steve Folly
2005-09-27 22:26 ` Daniel Jacobowitz
2005-09-28 11:52 ` Andrew STUBBS
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=20050927211834.GA20921@nevyn.them.org \
--to=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).