Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gerritvn@gpvno.co.za, gpvno@telkomsa.net
Cc: gdb@sourceware.org
Subject: Re: GDB/Mingw make problem
Date: Mon, 14 Jan 2008 04:05:00 -0000	[thread overview]
Message-ID: <u7iidqcgh.fsf@gnu.org> (raw)
In-Reply-To: <478A9781.31068.7269E5D@gerritvn.gpvno.co.za>

> From: "Gerrit van Niekerk" <gerritvn@gpvno.co.za>
> Date: Sun, 13 Jan 2008 22:58:09 +0200
> CC: gdb@sourceware.org
> 
> On 13 Jan 2008 at 22:04, Eli Zaretskii wrote:
> 
> > > From: "Gerrit van Niekerk" <gerritvn@gpvno.co.za>
> > > Date: Sun, 13 Jan 2008 21:18:26 +0200
> > > 
> > > The problem seems to be a very old version (v 3.02) of SED and I can't find a more recent one.
> > > Any help would be appreciated.
> > 
> > I think the GnuWin32 site has a newer version of Sed.
> 
> Thanks Eli, but the GnuWin32 copy of SED is not compatible with MinGW; it does the same as the 
> Cygwin copy of SED: It does not understand parameters passed by MSYS

Well, you didn't say anything about MSYS before.

I believe there's an MSYS version of Sed as well, check out the MinGW
site.

Failing that, building Sed is not a hard job, so just get the latest
sources from the GNU FTP site and build it with MSYS.


  reply	other threads:[~2008-01-14  4:05 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 [this message]
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
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=u7iidqcgh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=gerritvn@gpvno.co.za \
    --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