From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Charles-Henri <charles-henri@prolectronic.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] IMPORTANT ! for problem with GCC and INSIGHT build under CYGWIN !!!
Date: Mon, 12 Jun 2000 11:14:00 -0000 [thread overview]
Message-ID: <39452870.5FBECCC2@redhat.co.uk> (raw)
In-Reply-To: <001b01bfd38b$cadf2600$080dfea9@oemcomputer>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
> Charles-Henri wrote:
>
> Hello,
>
> for all users that want to build GCC and GDB under CYGWIN and an error
> occur with cygwin.dll version 1.1.1 or 1.1.2,
> I have a good news, I have found that is the "patch" command that
> transform output files in text mode with an \r in end
> of line, then the command "tr -d '\r' ecos-gcc-2952.pat ¦ patch -p0"
> create output file that make problem with make
> command.
I have verified on my cygwin 1.1.2 system that there are no problems
applying patches. I even did a fresh reinstall just to be sure.
The only situation I can imagine could cause problems would be if you
applied the patch using a textmode mount point, but then built via a
binmode mount point. But I tried that too, and that works!
So are you sure there isn't some other problem with your setup? If you (or
other people - anyone?) are having genuine problems here, help me find out
what the difference is between your setup and mine.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-06-12 11:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-11 2:59 Charles-Henri
2000-06-12 11:14 ` Jonathan Larmour [this message]
2000-06-13 15:24 ` [ECOS] NEC MIPS evlation board gcc build problem Ling Su
2000-06-13 15:45 ` [ECOS] " Jonathan Larmour
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=39452870.5FBECCC2@redhat.co.uk \
--to=jlarmour@redhat.co.uk \
--cc=charles-henri@prolectronic.com \
--cc=ecos-discuss@sourceware.cygnus.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).