Date: Sun, 20 Feb 2000 11:58:40 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: "Mark E." cc: djgpp-workers AT delorie DOT com Subject: Re: fileutils mkdir gotcha In-Reply-To: <200002192044.PAA26251@delorie.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 19 Feb 2000, Mark E. wrote: > The install process in binutils calls the 'mkinstalldirs' script which in > turn calls 'mkdir' from fileutils. The input to mkinstalldirs is this case > '/dev/env/DJDIR'. mkinstalldirs calls 'mkdir /dev' which it will create > (which is bad). Then calls 'mkdir /dev/env'. mkdir reports that the dir. > exists even though it doesn't (which in this case is good). And then > 'mkdir /dev/env/DJDIR' which reports that the dir exists (which it > should). The existing port of Fileutils was compiled with libc v2.01. If you want it to support /dev/env, you need to rebuild Fileutils with DJGPP v2.03 (yes, it's on my todo). As to the problem with /dev and /dev/env, I don't see why we should do anything. It is perfectly valid for a user to want to create /dev if they want that, and having that directory won't do any harm if you didn't mean for it to be created. As to having env created in the current directory, it's not nice indeed, but I rather think that mkinstalldirs is the wrong thing for DJGPP. It is much better to use "mkdir -p" instead. Perhaps Autoconf can do that when it senses the DJGPP environemnt, or if it finds GNU mkdir.