DOS EOL in multiline #define

DOS EOL in multiline #define

[John Watson]

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

Re: DOS EOL in multiline #define

[John Watson]

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

Re: DOS EOL in multiline #define

[John Watson]

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

DOS EOL in multiline #define

[John Watson]

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