From: Dave Murphy <wintermute2k4@ntlworld.com>
To: gerritvn@gpvno.co.za, gpvno@telkomsa.net
Cc: gdb@sourceware.org
Subject: Re: GDB/Mingw make problem
Date: Sat, 09 Feb 2008 00:48:00 -0000 [thread overview]
Message-ID: <47ACF852.8080909@ntlworld.com> (raw)
In-Reply-To: <478A8022.18277.6CAB521@gerritvn.gpvno.co.za>
Gerrit van Niekerk wrote:
> I am trying to make GDB-6.7.1 using MinGW on WinXP.
> Configure works fine:
>
> ./configure --host=i686-pc-mingw32 --target=djgpp
>
> Make gives the following error:
>
> sed -f .././bfd/targmatch.sed < .././bfd/config.bfd > targmatch.new
> sed: file .././bfd/targmatch.sed line 1: Extra characters after command
> make[4]: *** [targmatch.h] Error 1
>
> 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.
>
Actually, I had the same problem recently building from CVS. The problem
is that targmatch.sed has DOS line endings, msys sed 3.02 will cope fine
if you run dos2unix on the file first.
I didn't have this problem with the release tarballs though, just
TortoiseCVS being a pain & doing line conversions.
Dave
next prev parent reply other threads:[~2008-02-09 0:48 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
2008-02-09 0:48 ` Dave Murphy [this message]
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=47ACF852.8080909@ntlworld.com \
--to=wintermute2k4@ntlworld.com \
--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