This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Hmmm. the evidence looks pretty compelling to me - I'd agree with Richard's diagnosis. If you can't get hold of a clean file you can clean the one you've got on a Linux/Unix machine, if you've got access to one, using :- $ tr -d '\015' < arm.h > tmp $ mv tmp arm.h (I suggest that you take a quick look at tmp to check it looks sensible before you move it to arm.h) HTH Clive > -----Original Message----- > From: Andreas.Karlsson@combitechsystems.com > [mailto:Andreas.Karlsson@combitechsystems.com] > Sent: 28 June 2000 11:43 > To: rearnsha@arm.com > Cc: crossgcc@sourceware.cygnus.com > Subject: RE: Error in arm.h? > > > > Hi, > > The same error still occurs in spite of new downloads of both > gcc-core and > gcc-g++. > I'm running cygwin 1.1.0 on NT. I have downloaded and > succesfully installed > eCos 1.3.1. > > The objective of this project is to run eCos on ARM AEB-1 > evaluation board. > I just can't figure out why this error occurs when making gcc. > I attach my configure.out and make.out from the attempt to build gcc. > > /Andreas > > > > > > -----Original Message----- > From: Richard Earnshaw [mailto:rearnsha@arm.com] > Sent: den 27 juni 2000 15:52 > To: Karlsson Andreas > Cc: crossgcc@sourceware.cygnus.com; rearnsha@arm.com > Subject: Re: Error in arm.h? > > > > Hi, > > I'm a student trying to build the eCos operating system but > the following > > error occurs when building gcc. > > > /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: parse error before `{' > > /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:226: warning: > unknown escape > > sequence: `\' followed by char code 0xd > > /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:227: warning: > unknown escape > > sequence: `\' followed by char code 0xd > > It looks to me as though MS-DOG has got hold of your source > code. (0xd is > the DOG return character). This is then confusing the pre-processor. > > You need to get a clean copy of the source. > > R. > > > > ------ > Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |