To: djgpp-workers AT delorie DOT com Subject: Question about porting strategy. From: Michael Bukin Date: 21 Mar 1999 19:50:26 +0600 Message-ID: <20bthnlzod.fsf@Sky.inp.nsk.su> Lines: 34 X-Mailer: Gnus v5.5/Emacs 19.34 Reply-To: djgpp-workers AT delorie DOT com I was playing with guile (Scheme implementation) and along with some problems in configuration files I've run into some problems with not supported functionality in DJGPP. I think most of these problems were solved already for other packages, but I can not search through all of them, so I decided to ask here. Straight to the problems 1. This package uses fchown and fchmod routines, how should I emulate these correctly (or how to obtain file name from handle)? Right now I just call chown and chmod on "/dev/null". I think DOS will restrict accesses to already opened files and these functions are not that useful for DOS anyway. 2. There are tests for S_ISLNK and S_ISSOCK and also for S_IFLNK and S_IFSOCK. I recall that it was suggested just to define missing symbols if they are not already defined. Is it correct? And maybe these defines should be added in DJGPP anyway? I know that there is no such functionality, but libc calls just will not return those values and it can be used for some tweaking with FSEXT (I'm not sure about it). 3. This is not a problem, but just an idea. How feasible is it to add support for per program env file. Then each package can be distributed with its own env files which will be placed in standard directory under $DJDIR tree and which will be read after djgpp.env. Then it will not be necessary to add environment variables (for standard installation) and it can reduce incompatibilities between different versions of DJDEV and individual packages. Please, criticize this idea so I will not waste my time adding this functionality if it's not good for some reason. Thank you -- Michael Bukin