On Mon, 2003-11-17 at 21:56, Corinna Vinschen wrote: > On Sun, Nov 16, 2003 at 08:10:08AM +1100, Robert Collins wrote: > > We have two choices (no particular order of preference): > > a) make MAX_PATH and posix friends the maximum length path cygwin will > > accept/return. Return ENAMETOOLONG on path calls on win9x, or winnt > > FAT[32] calls. Update pathconf to return appropriate values. > > b) blow away MAX_PATH and MAXPATHLEN so that programs using cygwin > > fallback to pathconf, or 'good enough for me' static arrays. Update > > pathconf to return appropriate values. > > Well, I guess you meant PATH_MAX here.
Yes, of course. > I would prefer to change PATH_MAX and MAXPATHLEN to an arbitrary big > value as, e. g. the same as on Linux, 4096, or even the biggest possible > plus one: 32768. The latter is probably the better value. So my choice > is a) Ok. What should we set CYG_MAX_PATH to initially then? I think we should start at 4K, until we've seen whether there are any stack size issues. Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
signature.asc
Description: This is a digitally signed message part
