From: Wolfgang Denk <wd@denx.de>
To: Graf Alex <alex.graf@siemens.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: parse error before `{', stray '\' in program
Date: Thu, 10 Apr 2003 11:48:26 +0200 [thread overview]
Message-ID: <20030410094831.A1254C5877@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 10 Apr 2003 11:23:49 +0200." <791B3205DB661A42B4BFE5464A7D1D02010E44F3@chzugexch02.zug.ch.abatos.com>
In message <791B3205DB661A42B4BFE5464A7D1D02010E44F3@chzugexch02.zug.ch.abatos.com> you wrote:
>
> If I have some defines which have '\' inside ...
>
> #define BIND_DESC_ALM \
> { \
> CAlmSourceProp::IdxBindingGrp; \
> }
>
> my cross compiler produce following output:
>
> ppc_8xx-gcc -fPIC -DPIC -D_DEBUG -Wall -ansi -g3 -O0
> -I/home/projects/Nscu/_Inc -I/home/projects/Nscu/_Inc_PC -c -o main.o
> main.cpp
> main.cpp:15: parse error before `{'
> main.cpp:15: stray '\' in program
> main.cpp:16: stray '\' in program
This is usually caused by illegal file formats.
> The troubles are coming from the dos <cr><lf> at line end. With gcc 3.2
> (from host) I don't have this problems.
Use Unix file formats (plain '\n' line termination).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Brain off-line, please wait.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-10 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 9:23 parse error before `{', stray '\' in program Graf Alex
2003-04-10 9:48 ` Wolfgang Denk [this message]
[not found] <791B3205DB661A42B4BFE5464A7D1D02010E44F3@chzugexch02.zug.c h.abatos.com>
2003-04-10 16:47 ` Eugene Surovegin
[not found] <3E96684D.7000601@imc-berlin.de>
2003-04-11 7:24 ` Wolfgang Denk
2003-04-11 12:59 ` Ron Flory
[not found] <5.1.0.14.2.20030411103728.03024f68@mail.ebshome.net>
2003-04-11 19:04 ` Eugene Surovegin
2003-04-11 20:17 ` Wolfgang Denk
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=20030410094831.A1254C5877@atlas.denx.de \
--to=wd@denx.de \
--cc=alex.graf@siemens.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).