From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Watson To: help-gcc@gnu.org Subject: Re: DOS EOL in multiline #define Date: Thu, 06 Jan 2000 08:50:00 -0000 Message-id: <3874C1ED.28FC1025@stsci.edu> References: <3873C447.78441FE6@stsci.edu> X-SW-Source: 2000-01/msg00070.html 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Watson To: help-gcc@gnu.org Subject: Re: DOS EOL in multiline #define Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-ID: <3874C1ED.28FC1025@stsci.edu> References: <3873C447.78441FE6@stsci.edu> X-SW-Source: 2000-q1/msg00070.html Message-ID: <20000401000000.eZN0miwSqXtVEDey5Vz-5taODSCazQkGbq-cIay6OaM@z> 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