This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Help compiling gcc 4.2.0
- From: Brian Dessent <brian at dessent dot net>
- To: Lee Rhodes <lee at rhoba dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Thu, 21 Jun 2007 14:20:13 -0700
- Subject: Re: Help compiling gcc 4.2.0
- References: <000901c7b443$807135e0$0701a8c0@lee8075b>
- Reply-to: gcc-help at gcc dot gnu dot org
Lee Rhodes wrote:
> I am struggling with the infamous unix/dos end-of-line '\r\n' vs '\n'
> incompatibilities. It seems that no matter what shell I use (bash, sh,
> Cygwin, rxvt, dos) that the gnu make utility throws errors when it sees the
> '\r' CR character.
>
> Do I have to convert ALL the downloaded files into the unix format
> (dos2unix)? (Yikes!) or is there a global setting that I can use so that I
> don't have to do that.
There are no CRs anywhere in the source code tarballs. If you are
seeing any, they are a result of the method you used to unpack them
locally. This means you either didn't choose binary mode for your
mounts or you used a non-Cygwin tool such as Winzip to unpack the
tarballs. In either case, don't do that. There should never be a need
to convert anything.
Also, you'll need to use a Cygwin snapshot to build gcc otherwise you'll
run into <http://gcc.gnu.org/ml/gcc/2007-03/msg00948.html> which has
been fixed for some time, but the last Cygwin release was a while ago.
Brian