[BusyBox] [PATCH] PATH_MAX undefined in [u]mount.c

[Dan Kegel]

Neal H Walfield wrote:
> > > Neither POSIX nor the Single Unix Specification require PATH_MAX to be
> > > defined.
> >
> > http://www.opengroup.org/onlinepubs/007908799/xsh/limits.h.html
> > says otherwise.
> 
> Are you agreeing with me or disagreeing with me?  The link you gave me
> only confirms what I said:
> 
>   Pathname Variable Values
> 
>   The values in the following list may be constants within an
>   implementation or may vary from one pathname to another. For
>   example, file systems or directories may have different
>   characteristics.
> 
>   A definition of one of the values will be omitted from the
>   <limits.h> header on specific implementations where the
>   corresponding value is equal to or greater than the stated minimum,
>   but where the value can vary depending on the file to which it is
>   applied. The actual value supported for a specific pathname will be
>   provided by the pathconf() function.
> 
>   ...
> 
>   PATH_MAX
>     Maximum number of bytes in a pathname, including the terminating
>     null character. Minimum Acceptable Value: _POSIX_PATH_MAX

Ah, yes, I should have read more carefully. 

Practically speaking, though, most new os's define PATH_MAX in limits.h,
but my patch was to work around a screwed-up installation of gcc.

- Dan