From owner-freebsd-questions  Fri Aug 25  8:14:46 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from www3.pacific-pages.com (www3.pacific-pages.com [192.41.48.219])
	by hub.freebsd.org (Postfix) with ESMTP id BB80E37B42C
	for <questions@freebsd.org>; Fri, 25 Aug 2000 08:14:42 -0700 (PDT)
Received: from www3.pacific-pages.com ([216.191.60.195]) by www3.pacific-pages.com (8.8.5) id JAA29940; Fri, 25 Aug 2000 09:14:04 -0600 (MDT)
Message-ID: <39A68CE2.1D13C492@www3.pacific-pages.com>
Date: Fri, 25 Aug 2000 11:12:34 -0400
From: David Banning <david@www3.pacific-pages.com>
Reply-To: david@SkytrackerCanada.com
Organization: Sky-Tracker of Canada Inc.
X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Gus Mancuso <gus@fiawol.org>
Cc: questions@freebsd.org
Subject: Re: error on hylafax build
References: <200008242025.QAA04208@smof.fiawol.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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.
> 
> BTW, reply to me directly for faster response time, but make sure
> to cc the list, so people who know stuff can hear :)
> 
> Gus
> 
> > I am using 4.0 stable
> > hylafax is 4.1.b2
> >
> > first off, I get these errors
> > BoolArray.h: In method `void fxBoolArray::operator =(const fxBoolArray
> > &)':^M
> > BoolArray.h:31: warning: `void *' is not a pointer-to-object type^M
> >
> > then
> >
> > Dictionary.h: In method `void fxDictBuckets::operator =(const
> > fxDictBuckets &)':
> > ^M
> > Dictionary.h:93: warning: `void *' is not a pointer-to-object type^M
> > Dictionary.h: In method `void fxDictIters::operator =(const fxDictIters
> > &)':^M
> > Dictionary.h:94: warning: `void *' is not a pointer-to-object type^M
> > Dictionary.c++: In method `fxDictBucket::~fxDictBucket()':^M
> > Dictionary.c++:88: warning: `void *' is not a pointer-to-object type^M
> >
> > these type of errors continue for the entire build
> > any idea where the problem is?
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> >

-- 
The price of seeking to force our beliefs on others is that someday
they might force their beliefs on us.
		-- Mario Cuomo


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message