Hi Helmut, On 23/09/25 11:35 am, Helmut Grohne wrote: > On Tue, Sep 23, 2025 at 03:34:01AM +0530, Nilesh Patra wrote: >> +--- a/configure >> ++++ b/configure >> +@@ -641,6 +641,7 @@ > > You are patching a generated file here. The source file is configure.in.
Right, but as you did say below that the configure is not getting generated during the build, since d/rules has `dh $@ --without=autoreconf` and so patching configure.in does not solve the problem on at least debian side. Enabling autoreconf does not help either since there's no Makefile.am and there are other messy things in the codebase that I don't think can be fixed with the corresponding build files. So I am a bit confused on what exactly you think should be done here. Are you asking me to come up with a patch get it merged upstream so when the configure file is generated in their next release, it is more cross-friendly? If so, and if I were to be honest with you, looking at (seemingly tedious process at) https://xmlrpc-c.sourceforge.io/techsupp.php and seeing there are development releases that have moved forward (wrt current patch), it very much makes me not want to jump through the upstreaming hoop. Please let me know your thoughts. Best, Nilesh
