* DOS EOL in multiline #define
@ 2000-01-05 16:46 John Watson
2000-01-06 8:50 ` John Watson
2000-04-01 0:00 ` John Watson
0 siblings, 2 replies; 4+ messages in thread
From: John Watson @ 2000-01-05 16:46 UTC (permalink / raw)
To: help-gcc
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DOS EOL in multiline #define
2000-01-05 16:46 DOS EOL in multiline #define John Watson
@ 2000-01-06 8:50 ` John Watson
2000-04-01 0:00 ` John Watson
2000-04-01 0:00 ` John Watson
1 sibling, 1 reply; 4+ messages in thread
From: John Watson @ 2000-01-06 8:50 UTC (permalink / raw)
To: help-gcc
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DOS EOL in multiline #define
2000-01-06 8:50 ` John Watson
@ 2000-04-01 0:00 ` John Watson
0 siblings, 0 replies; 4+ messages in thread
From: John Watson @ 2000-04-01 0:00 UTC (permalink / raw)
To: help-gcc
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* DOS EOL in multiline #define
2000-01-05 16:46 DOS EOL in multiline #define John Watson
2000-01-06 8:50 ` John Watson
@ 2000-04-01 0:00 ` John Watson
1 sibling, 0 replies; 4+ messages in thread
From: John Watson @ 2000-04-01 0:00 UTC (permalink / raw)
To: help-gcc
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-04-01 0:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-01-05 16:46 DOS EOL in multiline #define John Watson
2000-01-06 8:50 ` John Watson
2000-04-01 0:00 ` John Watson
2000-04-01 0:00 ` John Watson
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).