GNOME Bugzilla – Bug 615618
MAXPATHLEN used unconditionally
Last modified: 2010-09-16 17:14:10 UTC
This is similar to https://bugzilla.gnome.org/show_bug.cgi?id=604493 MAXPATHLEN has been reintroduced. This patch makes use of dynamic allocation rather than fixed MAXPATHLEN size buffers, fixing the build on GNU/Hurd again. Would be nice to get it in 2.30.1
Created attachment 158575 [details] [review] Use dynamic allocation to avoid MAXPATHLEN
Created attachment 158576 [details] [review] Use dynamic allocation to avoid MAXPATHLEN, take 2 Meh, this one also frees the buffer before returning from the function :-) The MAXPATHLEN check is not needed since lstat should just return -1 with errno set to ENAMETOOLONG, so we don't need to manually check it.
Ping?
Created attachment 170042 [details] [review] Another fix for this problem. The last patch leaks memory when the function is successful. Does this patch do the trick for you? Let me know and I'll merge it.
Your patch looks much better than mine and is good to fix the FTBFS. Please commit it. Thanks!
Great. Patch was inlcuded in 2.31.92.