X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Fri, 12 Jun 2015 10:37:22 +0300 From: "Eli Zaretskii (eliz AT gnu DOT org)" Subject: Re: DJGGP 2.05 upgrade problems. In-reply-to: X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83616ts7gt.fsf@gnu.org> References: <201506091712 DOT t59HCPci004068 AT delorie DOT com> <557739E0 DOT 6070608 AT gmail DOT com> <55775E64 DOT 2090901 AT gmail DOT com> <5579ED42 DOT 6070309 AT gmail DOT com> 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 Precedence: bulk > Date: Thu, 11 Jun 2015 14:50:00 -0700 (PDT) > From: "rugxulo AT gmail DOT com" > > 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 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.