Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Patrick Doyle" <wpd AT delcomsys DOT com>
To:	"David Ryan" <oobles AT hotmail DOT com>, <cygwin AT cygwin DOT com>
Subject:	RE: Compiling Playstation2 cross compiler.
Date:	Wed, 11 Apr 2001 07:55:14 -0400
Message-ID:	<NFBBJAJICAKJPMMKDAGBGECACCAA.wpd@delcomsys.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To:	<008101c0c260$e30071c0$0900a8c0@robot>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.3018.1300

This sounds suspiciously similar to problems I remember having in the past
with some compilers but not others.  The two ideas that I would suggest for
you are 1) make sure you have the latest Cygwin release and 2) play around
with text vs. binary mounts.  For reasons I don't recall, I decided to just
mount everything in text mode a long time ago.  I haven't had CRLF problems
since then.  Others on the list recommend mounting your file systems in
binary mode for similar reasons.

--wpd


> -----Original Message-----
> From: cygwin-owner AT sources DOT redhat DOT com
> [mailto:cygwin-owner AT sources DOT redhat DOT com]On Behalf Of David Ryan
> Sent: Wednesday, April 11, 2001 4:25 AM
> To: cygwin AT cygwin DOT com
> Subject: Compiling Playstation2 cross compiler.
>
>
>
> Hi,
>
> I'm attempting to compile a Playstation2 (mips r5900) cross compiler which
> is based on gnu-gcc under cygwin.  I am currently having a
> problem with what
> seems to be related to CrLf problems.  The cc1.exe of the new compiler is
> failing to treat \\ \n (backslash followed by new lines) correctly for
> #define's.  It keeps reporting the error "stray '\' in program"
> where the \
> should be.  Removing the '\' and placing the complete define on one line
> seems to fix it, however, I'd prefer to fix the problem at the source.
>
> I've tried downloading the source for gcc from cygwin to see if I
> could see
> any major differences between source files but so far I've seen none.  I
> assume cygwin modified the compiler to look for these cases at some stage?
> How/Where was it done then?  The cross compiler has version 2.9-ee-991111b
> if thats any help.
>
> The assembler and linker have compiled and seem to be functioning
> correctly.
> The tar.gz file is available at ps2dev.sourceforge.net and is called
> gnu-ee-binutils-gcc-1.1.tar.gz on the download page.
>
> Its curently stopping at compiling libgcc2.c.  To get this far I have
> downloaded gettext and compiled and used its libintl.a file.  I've also
> modified rtl.c to check for '\r' in the functions read_skip_spaces and
> read_name.
>
> Any suggestions would be greatly appreciated,
> Thanks,
> David.
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -