X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Received:	by 10.129.82.214 with SMTP id g205mr17854996ywb.14.1434113818124;
	Fri, 12 Jun 2015 05:56:58 -0700 (PDT)
X-Received:	by 10.140.46.98 with SMTP id j89mr214289qga.13.1434113818107; Fri,
	12 Jun 2015 05:56:58 -0700 (PDT)
Newsgroups:	comp.os.msdos.djgpp
Date:	Fri, 12 Jun 2015 05:56:57 -0700 (PDT)
In-Reply-To:	<83616ts7gt.fsf@gnu.org>
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	glegroupsg2000goo.googlegroups.com; posting-host=65.13.115.246;
	posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
NNTP-Posting-Host:	65.13.115.246
References:	<201506091712 DOT t59HCPci004068 AT delorie DOT com> <557739E0 DOT 6070608 AT gmail DOT com>
	<CAB9Rao93XrKFBpUDnZdjCz+rEXHGOU2RNKdou2oMLJOk802LnA AT mail DOT gmail DOT com>
	<55775E64 DOT 2090901 AT gmail DOT com> <CAB9Rao-Njdr-CB=vqHnb+TVDmXu3eXqsB5CHB7V0kDwBEsM-WQ AT mail DOT gmail DOT com>
	<5579ED42 DOT 6070309 AT gmail DOT com> <bedfae3f-2695-4253-8d9c-11c55703f8b5 AT googlegroups DOT com>
	<83616ts7gt DOT fsf AT gnu DOT org>
User-Agent:	G2/1.0
MIME-Version:	1.0
Message-ID:	<510f0bc7-7911-4d22-bfca-48716371ecb5@googlegroups.com>
Subject:	Re: DJGGP 2.05 upgrade problems.
From:	"rugxulo AT gmail DOT com" <djgpp AT delorie DOT com>
Injection-Date:	Fri, 12 Jun 2015 12:56:58 +0000
Bytes:	3196
Lines:	39
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Hi,

N.B. Google Groups is misreporting the author here (Eli?).

On Friday, June 12, 2015 at 2:37:40 AM UTC-5, Frank Sapone (emoaddict15 AT hates DOT spam) wrote:
> > Date: Thu, 11 Jun 2015 14:50:00 -0700 (PDT)
> > From: "rugxulo AT hates DOT spam" <djgpp AT hates DOT spam>
> > > I also noticed find doesn't work 
> > > properly to delete all the previous *.o files.  Whatever previous 
> > > version of find I was using for 2.03 works fine.
> > > The way we were using it before is "find ./ -name '*.o' -exec rm {} \;".
> > > Now it spits out:
> > > rm : cannot remove './client/cl_cin.o' : No such file or directory (ENOENT).
> > 
> > Ignore find entirely! Use "rm .../*.o".
> 
> How's that going to help us find and fix all the problems in the new
> release of DJGPP?

I didn't think this was a serious issue. And it's very hard to debug
from guesswork without trying or seeing it yourself. Are you willing
to try to ssh into his machine? Do you want to check out his entire
project's sources and try to rebuild it?

I'm just saying, DJGPP has enough to worry with, but worrying about
minor tools is probably not (yet) top priority. Anyways, at the
very least, such things (Find or File+Txt+Shl) should probably
be recompiled with 2.05 *before* trying to debug anything.

> > > I am using Windows XP SP3 to compile if this helps.
> > 
> > XP usually works fairly well for DJGPP. Though I dunno, maybe there's
> > some (more) bugs. Maybe if subdirs nest too deeply? Try to avoid that.
> 
> He said the same worked with the old binaries, so I doubt this could
> be the reason.

I didn't catch that meaning, but maybe you're right. Again, I just don't
think it's realistic to worry about literally every minor nit here.
Certain things have to be higher priority.

- Raw text -