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

[Neal H Walfield]

> > > In some odd environments, <limits.h> doesn't define PATH_MAX
> > > as it should.  The workaround noted in ChangeLog is to include
> > > <sys/param.h>, but that workaround doesn't appear to be in
> > > [u]mount.c, which causes compilation to fail.
> > 
> > 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