Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<01f101c2916b$9a5539c0$1b4b82ce@connecttech.com>
From:	"Brandon Grenier" <bgrenier AT connecttech DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	m68k-elf-gcc problems under Cygwin
Date:	Thu, 21 Nov 2002 09:38:05 -0500
Organization:	Connect Tech Inc.
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
X-Virus-Scanned:	By Sentex Communications (avscan1/20020517)

Hi,

I'm having a problem running the m68k elf toolchain compiler under Cygwin.

I've downloaded the precompiled binary toolchain (m68k-elf-20020410.tar.gz)
from uClinux.org.

After unzipping (with gunzip) and untarring the toolchain, I *should* be
able to
use the m68k compiler 'right out of the box' so to speak.


The error message I am receiving is:

/m68k-elf-gcc: 1: Syntax error: "(" unexpected


I get the same error message whether I supply the compiler with arguments or
no arguments.


**Things I've done ( Under Windows98SE )

I downloaded the toolchain a three (3) different times. Each time I unpacked
the toolchain and tried to use the m68k compiler, with no luck.

I downloaded an older toolchain and tried out the m68k compiler again. I
still receive the same error message.


**Things I've done ( Under WIN2K )

I installed Cygwin again, and once again tried to use the m68k-elf-gcc
compiler, again receiving the same error message.


**Things I've done ( Under a Linux 2.4.X kernel )

Aha, the m68k-elf-gcc compiler does NOT give me the same error message.


**Things I've done ( google/newsgroups )

I've seen the same problem that I'm having on a ucLinux mailing list. There
was
no resolution ( aside from the suggestion to not use Cygwin ). Aside from
this
small thread, I haven't found anything useful.


From the testing above, my assumption is that something in the Cygwin
environment is not set up properly. However I'm not sure what it could be.

Has anyone ever encountered this problem before? Is there a resolution?

Cheers,

BG




--
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/

- Raw text -