From: Andris Pavenis To: djgpp AT delorie DOT com, Rob Kramer Subject: Re: 2.04 fsync buglet? Date: Fri, 11 Apr 2003 11:20:45 +0300 User-Agent: KMail/1.5.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304111120.45802.pavenis@latnet.lv> Reply-To: djgpp AT delorie DOT com On Friday 11 April 2003 10:41, Rob Kramer wrote: > Hey, > > When trying to cross compile 2.04 alpha, I had to apply the following tiny > fix: > > diff -c -3 -r1.2 fsync.c > *** src/libc/compat/unistd/fsync.c 26 Mar 2003 19:46:33 -0000 1.2 > --- src/libc/compat/unistd/fsync.c 11 Apr 2003 07:34:47 -0000 > *************** > *** 10,15 **** > --- 10,16 ---- > int > fsync(int _fd) > { > + __dpmi_regs r; > int oerrno = errno; > > /* Directory? If so, fail. */ > *************** > *** 19,25 **** > return -1; > } > > - __dpmi_regs r; > r.h.ah = 0x68; > r.x.bx = _fd; > __dpmi_int(0x21, &r); > --- 20,25 ---- > > > Hmm, now how could it have compiled for you guys with a variable > declaration in the middle of a function? > > revision 1.2 > date: 2003/03/26 19:46:33; author: richdawe; state: Exp; lines: +10 -0 > Fail for directories. > > Nobody compiled since 26/03, or am I missing something obvious? :) Verified results of my nightly automatic build: it built without problems with gcc-3.2.2 cross-compiler under Linux in 9 April without problems. Perhaps gcc-2.95.3 would complain, but gcc-3.2.2 does not. Also didn't notice it trying to build with gcc-3.3 snapshots (had to remove -Werror for that) Andris PS. By the way, one should not use gcc-3.1 for compiling djdev (it miscompiles at least one file). gcc-3.2.2 is OK.