{"thread":{"id":"65223","subject":"[PATCH] Fix GNU/Hurd build","startedAt":"2026-03-12T19:26:38Z","lastAt":"2026-03-16T06:41:29Z","messageCount":6,"participants":["Samuel Thibault","Junio C Hamano","Patrick Steinhardt"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"538799","messageId":"20260312191901.174808-1-samuel.thibault@ens-lyon.org","threadId":"65223","inReplyTo":null,"subject":"[PATCH] Fix GNU/Hurd build","fromName":"Samuel Thibault","fromEmail":"samuel.thibault@ens-lyon.org","sentAt":"2026-03-12T19:19:01Z","receivedAt":"2026-03-12T19:26:38Z","isPatch":true,"sender":{"key":"samuel.thibault@ens-lyon.org","avatar":"https://gravatar.com/avatar/fff265e7cec4e803a5627a6e839d72cc8f80ab86533031c5d4411da3aacea5e3?d=mp&s=160"},"body":"GNU/Hurd does not have a PATH_MAX limitation\n\nSigned-off-by: Samuel Thibault \n---\n t/unit-tests/clar/clar.h | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/t/unit-tests/clar/clar.h b/t/unit-tests/clar/clar.h\nindex f7e4363022..55b0361d91 100644\n--- a/t/unit-tests/clar/clar.h\n+++ b/t/unit-tests/clar/clar.h\n@@ -11,7 +11,7 @@\n #include \n #include \n \n-#if defined(_WIN32) && defined(CLAR_WIN32_LONGPATHS)\n+#if defined(__GNU__) || defined(_WIN32) && defined(CLAR_WIN32_LONGPATHS)\n # define CLAR_MAX_PATH 4096\n #elif defined(_WIN32)\n # define CLAR_MAX_PATH MAX_PATH\n-- \n2.51.0\n\n"},{"id":"538814","messageId":"xmqqbjgsdbr6.fsf@gitster.g","threadId":"65223","inReplyTo":"20260312191901.174808-1-samuel.thibault@ens-lyon.org","subject":"Re: [PATCH] Fix GNU/Hurd build","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-12T20:38:21Z","receivedAt":"2026-03-12T20:38:24Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Samuel Thibault writes:\n\n> GNU/Hurd does not have a PATH_MAX limitation\n\nThanks. clar folks might prefer to take it upstream and have us as\na downstream to import from them, so I'll forward it first before\ntaking it for ourselves.\n\nIt makes me wonder if an organization like this is easier to follow,\ni.e., platform specific settings first and then catch-all default at\nthe end:\n\n\t#if defined(CLAR_LONGPATHS)\n\t#define CLAR_MAX_PATH 4096\n\t#elif defined(PATH_MAX)\n\t#define CLAR_MAX_PATH PATH_MAX\n\t#elif deifned(MAX_PATH)\n\t#define CLAR_MAX_PATH MAX_PATH\n\t#fi\n\n\t#if !defined(CLAR_MAX_PATH)\n\t#define CLAR_MAX_PATH 4096\n\t#fi\n\nbut that is a separate issue best handled by the clar folks.\n\n\n--- >8 ---\nFrom: Samuel Thibault \nDate: Thu, 12 Mar 2026 20:19:01 +0100\nSubject: [PATCH] clar: compilation fix for GNU/Hurd\n\n fails to define CLAR_MAX_PATH on GNU/Hurd where PATH_MAX is\nnot defined.\n\nSigned-off-by: Samuel Thibault \nSigned-off-by: Junio C Hamano \n---\n t/unit-tests/clar/clar.h | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/t/unit-tests/clar/clar.h b/t/unit-tests/clar/clar.h\nindex ca72292ae9..4394aabbb9 100644\n--- a/t/unit-tests/clar/clar.h\n+++ b/t/unit-tests/clar/clar.h\n@@ -10,7 +10,7 @@\n #include \n #include \n \n-#if defined(_WIN32) && defined(CLAR_WIN32_LONGPATHS)\n+#if defined(__GNU__) || defined(_WIN32) && defined(CLAR_WIN32_LONGPATHS)\n # define CLAR_MAX_PATH 4096\n #elif defined(_WIN32)\n # define CLAR_MAX_PATH MAX_PATH\n-- \n2.53.0-707-gf7b889d8f7\n\n\n\n"},{"id":"538852","messageId":"abOxLFNGgZjo1dyi@pks.im","threadId":"65223","inReplyTo":"xmqqbjgsdbr6.fsf@gitster.g","subject":"Re: [PATCH] Fix GNU/Hurd build","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-03-13T06:39:40Z","receivedAt":"2026-03-13T06:39:45Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Mar 12, 2026 at 01:38:21PM -0700, Junio C Hamano wrote:\n> Samuel Thibault writes:\n> \n> > GNU/Hurd does not have a PATH_MAX limitation\n> \n> Thanks. clar folks might prefer to take it upstream and have us as\n> a downstream to import from them, so I'll forward it first before\n> taking it for ourselves.\n> \n> It makes me wonder if an organization like this is easier to follow,\n> i.e., platform specific settings first and then catch-all default at\n> the end:\n> \n> \t#if defined(CLAR_LONGPATHS)\n> \t#define CLAR_MAX_PATH 4096\n> \t#elif defined(PATH_MAX)\n> \t#define CLAR_MAX_PATH PATH_MAX\n> \t#elif deifned(MAX_PATH)\n> \t#define CLAR_MAX_PATH MAX_PATH\n> \t#fi\n> \n> \t#if !defined(CLAR_MAX_PATH)\n> \t#define CLAR_MAX_PATH 4096\n> \t#fi\n> \n> but that is a separate issue best handled by the clar folks.\n\nAgreed, something like this would read better indeed. Samuel, do you\nwant to maybe create a pull request in [1] to fix this in clar itself?\nYou can then give me (@pks-gitlab) a ping and I'll be happy to review\nit. I can then handle the subsequent pull request for Git.\n\nThanks!\n\nPatrick\n\n[1]: https://github.com/clar-test/clar\n"},{"id":"538917","messageId":"abRIXE2es5A-4VLv@end","threadId":"65223","inReplyTo":"abOxLFNGgZjo1dyi@pks.im","subject":"Re: [PATCH] Fix GNU/Hurd build","fromName":"Samuel Thibault","fromEmail":"samuel.thibault@ens-lyon.org","sentAt":"2026-03-13T17:24:44Z","receivedAt":"2026-03-13T17:24:46Z","isPatch":true,"sender":{"key":"samuel.thibault@ens-lyon.org","avatar":"https://gravatar.com/avatar/fff265e7cec4e803a5627a6e839d72cc8f80ab86533031c5d4411da3aacea5e3?d=mp&s=160"},"body":"Patrick Steinhardt, le ven. 13 mars 2026 07:39:40 +0100, a ecrit:\n> On Thu, Mar 12, 2026 at 01:38:21PM -0700, Junio C Hamano wrote:\n> > Samuel Thibault writes:\n> > \n> > > GNU/Hurd does not have a PATH_MAX limitation\n> > \n> > Thanks. clar folks might prefer to take it upstream and have us as\n> > a downstream to import from them, so I'll forward it first before\n> > taking it for ourselves.\n> > \n> > It makes me wonder if an organization like this is easier to follow,\n> > i.e., platform specific settings first and then catch-all default at\n> > the end:\n> > \n> > \t#if defined(CLAR_LONGPATHS)\n> > \t#define CLAR_MAX_PATH 4096\n> > \t#elif defined(PATH_MAX)\n> > \t#define CLAR_MAX_PATH PATH_MAX\n> > \t#elif deifned(MAX_PATH)\n> > \t#define CLAR_MAX_PATH MAX_PATH\n> > \t#fi\n> > \n> > \t#if !defined(CLAR_MAX_PATH)\n> > \t#define CLAR_MAX_PATH 4096\n> > \t#fi\n> > \n> > but that is a separate issue best handled by the clar folks.\n> \n> Agreed, something like this would read better indeed.\n\nAh, actually Pino already contributed a fix in december:)\n\n> Samuel, do you\n> want to maybe create a pull request in [1] to fix this in clar itself?\n\n> [1]: https://github.com/clar-test/clar\n\nIt would be useful to put this github url in the README, I have\nsubmitted\nhttps://github.com/clar-test/clar/pull/135\nso it'll eventually end up in the git source for people to find out\nwhere to send clar patches.\n\nSamuel\n"},{"id":"538923","messageId":"xmqqsea34kdy.fsf@gitster.g","threadId":"65223","inReplyTo":"abRIXE2es5A-4VLv@end","subject":"Re: [PATCH] Fix GNU/Hurd build","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-03-13T19:08:57Z","receivedAt":"2026-03-13T19:09:01Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Samuel Thibault writes:\n\n>> Agreed, something like this would read better indeed.\n>\n> Ah, actually Pino already contributed a fix in december:)\n\nGood to know.\n\n> It would be useful to put this github url in the README, I have\n> submitted\n> https://github.com/clar-test/clar/pull/135\n> so it'll eventually end up in the git source for people to find out\n> where to send clar patches.\n\nWonderful. Thanks.\n"},{"id":"539067","messageId":"abemE08uzRwB-xwp@pks.im","threadId":"65223","inReplyTo":"abRIXE2es5A-4VLv@end","subject":"Re: [PATCH] Fix GNU/Hurd build","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-03-16T06:41:23Z","receivedAt":"2026-03-16T06:41:29Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Mar 13, 2026 at 06:24:44PM +0100, Samuel Thibault wrote:\n> Patrick Steinhardt, le ven. 13 mars 2026 07:39:40 +0100, a ecrit:\n> > On Thu, Mar 12, 2026 at 01:38:21PM -0700, Junio C Hamano wrote:\n> > > Samuel Thibault writes:\n> > > \n> > > > GNU/Hurd does not have a PATH_MAX limitation\n> > > \n> > > Thanks. clar folks might prefer to take it upstream and have us as\n> > > a downstream to import from them, so I'll forward it first before\n> > > taking it for ourselves.\n> > > \n> > > It makes me wonder if an organization like this is easier to follow,\n> > > i.e., platform specific settings first and then catch-all default at\n> > > the end:\n> > > \n> > > \t#if defined(CLAR_LONGPATHS)\n> > > \t#define CLAR_MAX_PATH 4096\n> > > \t#elif defined(PATH_MAX)\n> > > \t#define CLAR_MAX_PATH PATH_MAX\n> > > \t#elif deifned(MAX_PATH)\n> > > \t#define CLAR_MAX_PATH MAX_PATH\n> > > \t#fi\n> > > \n> > > \t#if !defined(CLAR_MAX_PATH)\n> > > \t#define CLAR_MAX_PATH 4096\n> > > \t#fi\n> > > \n> > > but that is a separate issue best handled by the clar folks.\n> > \n> > Agreed, something like this would read better indeed.\n> \n> Ah, actually Pino already contributed a fix in december:)\n\nOh, you're right! I'll send an update to the latest clar version later\ntoday.\n\n> > Samuel, do you\n> > want to maybe create a pull request in [1] to fix this in clar itself?\n> \n> > [1]: https://github.com/clar-test/clar\n> \n> It would be useful to put this github url in the README, I have\n> submitted\n> https://github.com/clar-test/clar/pull/135\n> so it'll eventually end up in the git source for people to find out\n> where to send clar patches.\n\nMakes sense, thanks.\n\nPatrick\n"}]}