From: John Watson <jwatson@stsci.edu>
To: help-gcc@gnu.org
Subject: Re: DOS EOL in multiline #define
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <3874C1ED.28FC1025@stsci.edu> (raw)
Message-ID: <20000401000000.eZN0miwSqXtVEDey5Vz-5taODSCazQkGbq-cIay6OaM@z> (raw)
In-Reply-To: <3873C447.78441FE6@stsci.edu>
ok i found a solution to this problem reported by Matthias Klose
in Debian bug report log #29240. The solution is to use gcc-2.95.
I currently use gcc-2.91.66 on Redhat 6.1, which is part of the
egcs-1.1.2-24 package.
Does anyone know where I can obtain newer rpm files which I can
use to upgrade my gcc version to 2.95? I would prefer not to
have to remove the packages and manually install the compilers.
I have looked on rpmfind.net and grabbed the following rpms:
binutils-2.9.5.0.22-1.i386.rpm egcs-2.91.66-5.i386.rpm
cpp-2.95.2-3.i386.rpm egcs-c++-2.91.66-5.i386.rpm
However, testing the upgrade indicates the following errors:
# rpm --test -Uvh egcs-*.rpm binutils-2.9.5.0.22-1.i386.rpm cpp-2.95.2-3.i386.rpm
file /usr/include/ansidecl.h conflicts between attemped installs of binutils-2.9.5.0.22-1 and egcs-2.91.66-5
file /usr/lib/libiberty.a conflicts between attemped installs of binutils-2.9.5.0.22-1 and egcs-2.91.66-5
file /lib/cpp conflicts between attemped installs of cpp-2.95.2-3 and egcs-2.91.66-5
Thanks,
JW
John Watson wrote:
>
> I am trying to compile a c program with gcc.
> The c source file in in DOS format, so all the EOL's have
> that extra annoying ^M. Unfortunately, gcc craps out on
> multiline #defines during the compile.
>
> Is there any way to make gcc ignore the ^M's without
> converting the source file to a sane format?
>
> I tried using
> #define ^M ""
>
> but, gcc says that the ^M character is not a valid macro name.
>
> Thanks,
> JW
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-05 16:46 John Watson
2000-01-06 8:50 ` John Watson [this message]
2000-04-01 0:00 ` John Watson
2000-04-01 0:00 ` John Watson
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=3874C1ED.28FC1025@stsci.edu \
--to=jwatson@stsci.edu \
--cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).