From: Ron Flory <ron.flory@adtran.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: parse error before `{', stray '\' in program
Date: Fri, 11 Apr 2003 07:59:21 -0500 [thread overview]
Message-ID: <3E96BC29.1020903@adtran.com> (raw)
In-Reply-To: 20030411072503.64755C5877@atlas.denx.de
Wolfgang Denk wrote:
> In message <3E96684D.7000601@imc-berlin.de> you wrote:
>
>>Good you please post the URL to the list if you find one!
>>I am facing this problem from time to time ...
>>
>>Does anyone know if the ppc_8xx-gcc 2.95.4 from DENX ELDK has this
>>patch applied?
>
>
> No, it has not, and will not.
>
> I see no sense in a modification that supports violations of the C
> standard.
especially when its so easy to cleanup text files by piping them
through 'tr':
cat "$src_file" | tr -d \\015 > "$tmp_file"
mv -f $tmp_file $src_file
which removes those funky MsDos carriage returns.
(depending on your shell, you may be able to skip the tmp_file above)
Just write a small shell-script that iterates through your source
files, applying this filter.
Like you, I also develop on several platforms. I find it convenient
to add a new 'fix' target to the makefiles, then run the above filter
on all source and header files in the project.
<import file from MsDos/windoze>
make fix # with implied 'make clean'
make
works great, on lots and lots of projects...
ron
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-11 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E96684D.7000601@imc-berlin.de>
2003-04-11 7:24 ` parse error before `{', stray '\' in program Wolfgang Denk
2003-04-11 12:59 ` Ron Flory [this message]
[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
[not found] <791B3205DB661A42B4BFE5464A7D1D02010E44F3@chzugexch02.zug.c h.abatos.com>
2003-04-10 16:47 ` Eugene Surovegin
2003-04-10 9:23 Graf Alex
2003-04-10 9:48 ` 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=3E96BC29.1020903@adtran.com \
--to=ron.flory@adtran.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
/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).