This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Problems making gcc
- To: ecos-discuss at sources dot redhat dot com
- Subject: Re: [ECOS] Problems making gcc
- From: Hugo 'NOx' Tyson <hmt at cygnus dot co dot ukx>
- Date: 09 Jun 2000 12:10:57 +0100
- CC: alexs at sourceware dot cygnus dot com, jens dot ohlund at secrc dot abb dot se
- Newsgroups: cygnus.sourceware.ecos.d
- Organization: Cygnus Solutions, a Red Hat company (Cambridge, UK)
- References: <OFC5B1690C.5916E849-ONC12568F9.00320CEE@secrc.abb.se>
jens.ohlund@secrc.abb.se writes:
> My problem is that even if i follow the given instructoins it crashes...
>
> I run NT4 and i want to install ecos 1.3.1 with insight for the ARM. (AEB-1).
> /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
> /src/gcc/gcc-2.95.2/gcc/config/arm/arm.h:228: warning: unknown escape sequence: `\' followed by char code 0xd
>
> And it continues like that ALOT.
I don't know a fix (not being an NT user) but the cause is line endings.
The compiler expects '\' '<newline>' to do continuation lines, but it is
seeing '\' '<return>' '<newline>'.
Therefore a) warning about unknown escape sequence, and b) much worse,
continuation lines in macro definitions do not work at all, so it all goes
horribly wrong.
Mount modes, binary vs. text?
Or down to not setting "binary" in ftp when you acquired/copied/moved the
original sources? (though that usually snafus up a compressed archive lots
worse)
ISTR talking to our man Al, whom I have copied this msg, about a similar
thing yesterday. Al, can you shed any light on this?
- Huge