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
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
X-Mailer: MIME-tools 4.103 (Entity 4.115)
From: <tvoverbe AT cistron DOT nl>
Date: Fri, 3 Aug  2001 16:28:50
To: qiaogp AT krdl DOT org DOT sg
Subject: Re: arm gcc on cygwin
Cc: starksb AT ebi DOT ac DOT uk, cygwin AT cygwin DOT com
Message-Id: <E15SfwY-0007wL-00@smtp1.cistron.nl>

As David wrote, you get this on cygwin also for m68k-palmos.
For m68k-palmos the cause is that the directory where the gcc specs file
is read from is mounted binary under cygwin, but the specs file has DOS CR/LF line-endings.
I bet you the same is the case for you with arm-elf-gcc.
Find the location of the specs file (arm-elf-gcc -v' will
tell you) and check the mount of that directory and specs file line-endings.
If the mount is binary convert the specs file to Unix style LF only endings and 
everything will be fine.

Hope this helps.

Ton van Overbeek

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/