Date: Fri, 25 Aug 2000 11:23:04 -0400 From: Allen Landsidel <all@biosys.net> To: questions@FreeBSD.ORG Subject: Re: error on hylafax build Message-ID: <4.3.2.7.2.20000825112043.00b4e198@mail.megapathdsl.net> In-Reply-To: <39A68CE2.1D13C492@www3.pacific-pages.com> References: <200008242025.QAA04208@smof.fiawol.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:12 08/25/2000 -0400, David Banning wrote: >My installation has no relation to dos - I know about the ^M thing, >which I have only run into in with dos stuff. The ^M in this case, >happens when I go "script logfile make" in the /usr/ports/comms/hylafax >directory - for some reason it's always shown ^M's in the logfile >when I do it as above, - but it's never been related to any problems >I've had. > > >Gus Mancuso wrote: > > > > I'll stab at this since apparently noone else has. Keep in mind > > I'm no Code Wizard. I don't know if it's just a copyover error, > > but the ^M's you show there typically come from using "dos" text > > files without having the cr/lf incompatibilities resolved. > > So, did you copy the source files from some other MS machine, > > or was this from a tarball? Do the ^M's actually appear in the > > errors? Are the errors appearing on the console, or did you pipe > > it to a file? > > > > If the text is stored in the dos cr/lf mode, there is a package > > called dos2unix which will automagically fix that.. Combine it > > with a quick perl (or shell) script to fix an entire source tree. It's also trivially easy to remove these files with a single sed command, no real need for any sort of dos2perl comes to my mind, simply.. sed s/^M// infile > outfile To get the ^M in the shell, just hit ctrl-V and then ctrl-M which will escape it for you from the shell. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20000825112043.00b4e198>