Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Gerrit van Niekerk" <gerritvn@gpvno.co.za>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: DJ Delorie <dj@redhat.com>,               gdb@sourceware.org
Subject: Re: GDB/Mingw make problem
Date: Tue, 15 Jan 2008 16:04:00 -0000	[thread overview]
Message-ID: <478CF5A3.27246.5DB96B6@gerritvn.gpvno.co.za> (raw)
In-Reply-To: <478C9398.407@st.com>

On 15 Jan 2008 at 11:06, Andrew STUBBS wrote:

> If you don't use -mno-cygwin then gcc *will* use cygwin headers. 
> Otherwise, if you do use -mno-cygwin, then it still might - the search 
> paths are not quite right - but usually only as a fall back if there 
> isn't a mingw header of that name.

Thanks for everyone who gave me tips. I decided to reduce complexity and rather build for a Cygwin 
host. I also downloaded the latest CVS snapshot of GDB which got rid of the libintl.h problem. I am 
still not able to even build a Cygwin build, host and target version of GDB, but that should be 
another thread.





  reply	other threads:[~2008-01-15 16:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 19:18 Gerrit van Niekerk
2008-01-13 20:05 ` Eli Zaretskii
2008-01-13 20:59   ` Gerrit van Niekerk
2008-01-14  4:05     ` Eli Zaretskii
2008-01-14 16:42       ` Gerrit van Niekerk
2008-01-14 16:45         ` Bob Rossi
2008-01-14 17:41         ` Andrew STUBBS
2008-01-14 17:43         ` Andrew STUBBS
2008-01-14 20:39           ` Eli Zaretskii
2008-01-14 21:13             ` DJ Delorie
2008-01-15  7:33               ` Gerrit van Niekerk
2008-01-15 11:07                 ` Andrew STUBBS
2008-01-15 16:04                   ` Gerrit van Niekerk [this message]
2008-02-09  0:48 ` Dave Murphy
2008-02-10 19:35   ` Gerrit van Niekerk

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=478CF5A3.27246.5DB96B6@gerritvn.gpvno.co.za \
    --to=gerritvn@gpvno.co.za \
    --cc=andrew.stubbs@st.com \
    --cc=dj@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=gpvno@telkomsa.net \
    /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