Mail Archives: cygwin/2003/11/22/06:03:35
--=-vSV57PhxkL1blt0CUVdf
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Sat, 2003-11-22 at 21:59, Corinna Vinschen wrote:
> > However, CYG_MAX_PATH is simply decoupling the win32 ANSI path limit
> > from our internal path limit. If and when we don't have an effective
> > internal limit anymore, sure it can go.
>=20
> Yup, that's what I meant. It doesn't hurt to check the occurences
> of CYG_MAX_PATH now, if there isn't a simple way to get around without
> it. Other than that, I think the right limit is 32K as I already wrote
> in my first reply (see above), not something less than that. Using
> some arbitrary number like 4K only results in headaches at a point
> where you had never expected it. The difference to Linux is, that 4K
> is the real limit on Linux, while our limit is 32K.
Ok. Well, once we have the bugs ironed out, lets bump PATH_MAX to 32K,
and let the recompilation begin :}.
I'll probably put a few test binaries together in a setup.exe repository
- ash, bash, tar, gzip as a minimum for folk to play with, when the
patch gets closer to full completion.
Rob
--=20
GPG key available at: <http://www.robertcollins.net/keys.txt>.
--=-vSV57PhxkL1blt0CUVdf
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/v0J3I5+kQ8LJcoIRAuCxAJ45PbKy7gLkbNY3i8vcFnj8iQgPOwCgqKEV
gxsRWQQva0oMdg0QOA6liT0=
=VEsr
-----END PGP SIGNATURE-----
--=-vSV57PhxkL1blt0CUVdf--
- Raw text -