> It's nice that you consider enhancing gnulib-tool.py. But don't
underestimate
the task:
Yes, this suggestion was _only_ to support situations where no
automake-subdir was required and we stripped the path.I have automated
several build packages so could likely automate testing of the
gnulib-
In GNU gettext, I see these warnings when compiling with gcc 13, warnings,
and -O2:
gettext-tools/gnulib-lib/classpath.c:97:1: warning: function might be candidate
for attribute 'malloc' [-Wsuggest-attribute=malloc]
gettext-tools/gnulib-lib/csharpexec.c:36:23: warning: function might be
candidat
Hi Mitch,
> I hope to have some semi-quality patches to submit soon enough.
> ...
> I do see sed being used in a few other places. Of
> course I could likely put a patch together to emulate that in python as
> well.
It's nice that you consider enhancing gnulib-tool.py. But don't underestimate
th
Paul Eggert wrote:
> +/* Return the localization of the name spelled NAME_ASCII in ASCII,
> + and NAME_UTF8 in UTF-8. This function needs less infrastructure
> + than proper_name and proper_name_utf8. */
> +extern const char *proper_name_lite (const char *name_ascii,
> +
Paul Eggert wrote:
> * pygnulib/GLEmiter.py (GLEmiter.po_Makevars):
> Treat proper_name_lite like proper_name_utf8.
The preferred implementation of gnulib-tool is still the shell script.
Therefore we need to do gnulib-tool changes to both implementations, in sync.
I'm therefore applying this:
20
Paul Eggert wrote:
> > How about changing this to use __builtin_constant_p instead of
> > __OPTIMIZE__? I.e., use the comma expression if __builtin_constant_p
> > (status), and use the statement expression otherwise.
>
> I gave that a shot by installing the attached.
Oh, I see now what you mean
