From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sourceware.cygnus.com
Cc: alexs@sourceware.cygnus.com, jens.ohlund@secrc.abb.se
Subject: Re: [ECOS] Problems making gcc
Date: Fri, 09 Jun 2000 04:15:00 -0000 [thread overview]
Message-ID: <pt66rjp0se.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <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
WARNING: multiple messages have this Message-ID
From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sources.redhat.com
Cc: alexs@sourceware.cygnus.com, jens.ohlund@secrc.abb.se
Subject: Re: [ECOS] Problems making gcc
Date: Wed, 05 Sep 2001 00:10:00 -0000 [thread overview]
Message-ID: <pt66rjp0se.fsf@masala.cygnus.co.uk> (raw)
Message-ID: <20010905001000.aRUOacx-mAS0WZfEFkMEEXUWX3NTm7yIK3WsuMANeg4@z> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2000-06-09 4:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-09 2:18 jens.ohlund
2000-06-09 4:15 ` Hugo 'NOx' Tyson [this message]
2000-06-09 4:26 ` Alex Schuilenburg
2000-06-09 7:37 ` Jonathan Larmour
2001-09-05 0:10 ` Hugo 'NOx' Tyson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pt66rjp0se.fsf@masala.cygnus.co.uk \
--to=hmt@cygnus.co.ukx \
--cc=alexs@sourceware.cygnus.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jens.ohlund@secrc.abb.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).