[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

fchown-stub.c not pulled in for DJGPP 2.03p2

From: Rugxulo
Subject: fchown-stub.c not pulled in for DJGPP 2.03p2
Date: Tue, 21 Jul 2009 21:47:38 -0500

   I'm really not trying to be a pest, honest, but I personally still
use DJGPP (on Vista, XP, and real DOS [MS- / DR- / Free-], even).
DJGPP still hasn't ever finished the final 2.04, so it's stuck at
beta. Hence the DJGPP guys still port stuff to both 2.03p2 and 2.04.
DJGPP 2.04 beta does have fchown() but 2.03p2 "stable" (tested a lot
more) doesn't. Hence you already have fchown-stub.c. But it isn't
being pulled in for some reason (e.g. ZILE 2.3.9). It's not like I
can't hack the makefile to do so, but I'm just saying ... might be a

P.S. Two other things I already mentioned but may be of no use to use

1). My suggested code snippet for detecting "selected display CON
codepage" in MS- / DR- / FreeDOS / Win9x (but not XP, Vista, etc),
e.g. for localcharset.c. I've been told that DOS isn't relevant
anymore, but FreeDOS is GPL and still updated (see June's kernel 2038
release) as is DJGPP (well, ports of GCC 4.4.0 and sed 4.2 [Gnulib!],
at least).

2). Vista by default (non-Admin) doesn't like MSVCRT.DLL's / MSVC 6's
tmpfile(), at least in all the paq8 series (Matt Mahoney, et al). This
is one reason I use DJGPP, no such problems (despite Windows bugs).
I'm told you have a tmpfile() replacement somewhere, but I've never
checked yet. (I already worked around the issue in source via some
really dumb hackish way myself.) In fact, the Win32 compile of
AdvanceComp (advzip, advdef) stopped working recently, which I blame
on Vista SP2 (gah, what the heck ...), yet another example of DJGPP
working around the problem (and yes, I know, DPMI limit bug ... but
SP1 + registry hack fixed that although Win2k3 is still broken, bad MS

In short, DJGPP sometimes works where MinGW does not. (Yes, Cygwin
works but has license issues and is slower. But at least Cygwin and
DJGPP libs can be bugfixed if necessary.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]