From: Steve Folly <gdb-list@spfweb.co.uk>
To: GDB List <gdb@sources.redhat.com>
Subject: Re: Can't build gdb for mingw32 if not native? :-(
Date: Wed, 28 Sep 2005 20:08:00 -0000 [thread overview]
Message-ID: <AD89E4BF-E8D5-4D3E-9061-A74544D9BAD0@spfweb.co.uk> (raw)
In-Reply-To: <433A7285.9060207@st.com>
On 28 Sep 2005, at 11:37, Andrew STUBBS wrote:
>
> The top level configure script may do, but as Daniel says the GDB
> sources do not.
I see now. I'm new to configure scripts. :-)
>
> 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.
Some of our apps run full screen and having a remote machine to debug
on helps quite a bit.
I guess dual-screen capable PCs will help here, but our current
hardware (supplied by our customer) doesn't support that.
>
> 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.
>
I think Cygwin may be the way to go - some makefiles we have running
on OS X are using utilities like sed and grep, and we'd like to port
them to Windows with the minimum of fuss.
Thanks very much for your advice.
--
Regards,
Steve.
next prev parent reply other threads:[~2005-09-28 20:08 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
2005-09-28 20:08 ` Steve Folly [this message]
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=AD89E4BF-E8D5-4D3E-9061-A74544D9BAD0@spfweb.co.uk \
--to=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).