Message-Id: <200002201730.MAA00147@delorie.com>
From: "Mark E." <snowball3 AT bigfoot DOT com>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Sun, 20 Feb 2000 12:38:11 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: fileutils mkdir gotcha
References: <200002192044 DOT PAA26251 AT delorie DOT com>
In-reply-to: <Pine.SUN.3.91.1000220115759.25009s-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12a)
Reply-To: djgpp-workers AT delorie DOT com

> 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).
> 

The problems I described were with a rebuilt Fileutils 3.16. Perhaps this 
side effect of mkinstalldirs (that you'll get a /dev directory and a env 
directory) with '/dev/env/DJDIR' should be mentioned somewhere?

If it doesn't conflict with your todo list, I'd like to upload a binutils 2.9.5 beta 
and perhaps update Bison to 1.28. One thing I'd like to do to is give Bison 
it the ability to generate y.tab.c in LFN mode (kinda like makeinfo and split 
info files), unless overriden by BISION_LFN_OUTPUT. Is this ok with folks 
and will it create any problems?

Mark