On Fri, Apr 27, 2018 at 09:33:55AM +0200, Uwe Kleine-König wrote: > On 04/27/2018 09:33 AM, Luc Van Oostenryck wrote: > > On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote: > >> Hello, > >> > >>> [..] > >> > >> Just a heads up: I uploaded 0.5.2 to Debian and there are problems left > >> on hurd-i386 (where PATH_MAX isn't defined[1]) > >> ... > >> [1] > >> https://buildd.debian.org/status/fetch.php?pkg=sparse&arch=hurd-i386&ver=0.5.2-1&stamp=1524168405&raw=0 > > > > Thanks for the repport. > > I'll see what can be done. > > I think the default idiom is: > > #ifndef PATH_MAX > #define PATH_MAX 4096 > #endif Yes. I had hoped to avoid this together with removing a memcpy() but things are more annoying than I had first thought. Best regards, -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
