[rrd-developers] RFC: [PATCH] Portability by avoiding PATH_MAX

Steve Schnepp steve.schnepp at gmail.com
Thu May 8 02:41:25 CEST 2014

Le 7 mai 2014 16:10, "Tobias Oetiker" <tobi at oetiker.ch> a écrit :
> Today Svante Signell wrote:

> > Well, the PATH_MAX patches affect all architectures, but without them
> > rrdtool FTBFS for Hurd. For other architectures, like Linux, the code
> > should work the same. With the patches memory is allocated on the heap,
> > without on the stack. There should be no memory leaks in either case.
> ok :-) that might be a bit tricky

Would it be acceptable to revert to malloc() if and only if PATH_MAX is not
defined ?

That would nicely minimize the patch impact on already working platforms.

Steve Schnepp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/rrd-developers/attachments/20140508/4ad57580/attachment.htm 

More information about the rrd-developers mailing list