X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f Date: Sat, 06 Apr 2002 20:13:53 +0300 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: badri8088 AT yahoo DOT com (badri8088) Message-Id: <2593-Sat06Apr2002201352+0300-eliz@is.elta.co.il> X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: djgpp AT delorie DOT com In-reply-to: <2cf22887.0204060454.742703c0@posting.google.com> (badri8088 AT yahoo DOT com) Subject: Re: Chess chaos! References: <2cf22887 DOT 0204060454 DOT 742703c0 AT posting DOT google 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 > From: badri8088 AT yahoo DOT com (badri8088) > Newsgroups: comp.os.msdos.djgpp > Date: 6 Apr 2002 04:54:34 -0800 > > I got the foll output-- > C:\djgpp\openproj1\gnuchess-5.04\src>make > gcc -c -o atak.o atak.c > In file included from common.h:638, > from atak.c:29: > inlines.h: In function `leadz': > inlines.h:43: warning: right shift count >= width of type > inlines.h:43: warning: right shift count >= width of type > inlines.h:44: warning: right shift count >= width of type > inlines.h:44: warning: right shift count >= width of type > inlines.h: In function `nbits': > inlines.h:57: warning: right shift count >= width of type > inlines.h:57: warning: right shift count >= width of type > -------------------------------------------------------------- > make stops here . > what command should i give make to continue in-spite of errors & > warnings(as above) ?? Warnings should not stop Make, so you shouldn't need to do anything. There's probably some other error (not warning) that causes it to stop. In any case, you are well advised to look closely at the source code which triggers these warnings: they could cause real bugs in the program. > whats "uint64_t" in common.h ?? I'm guessing that it's an unsigned 64-bit integral type, i.e. "unsigned long long". You should see a typedef for it somewhere in the headers or sources of that program.