Jim Meyering wrote:
> Is there an advantage to using the system getcwd for names
> shorter than PATH_MAX, as there is on Solaris and systems with
> a linux kernel? (i.e., ability to function in spite of restricted
> permissions on a parent directory)
Paul Eggert wrote:
> The first patch is simpler
On 11/20/11 11:27, Bruno Haible wrote:
> Either of the two following patches fixes it. Which one do you prefer?
The first patch is simpler and easier to maintain, so I'd go with it
unless there's a performance or correctness reason to go with the
second patch.
In Solaris, the system getcwd has s
ons on a parent directory)
If so, I think we must prefer the latter, even though it incurs
the additional overhead (albeit only on AIX) of two lstat calls per
component.
> 2011-11-20 Bruno Haible
>
> getcwd: Work around getcwd bug on AIX 5..7.
> * lib/getcwd
n AIX 5..7.
* lib/getcwd.c (__getcwd): Don't use the system's getcwd on AIX.
* doc/posix-functions/getcwd.texi: Mention list of platforms where
getcwd does not handle long file names.
--- lib/getcwd.c.orig Sun Nov 20 19:19:55 2011
+++ lib/getcwd.cSun Nov 20 19:
