bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #65811] gettext 0.22 fails on centos 7 / gcc 4.8 due to gnulib auto


From: Bruno Haible
Subject: [bug #65811] gettext 0.22 fails on centos 7 / gcc 4.8 due to gnulib autosprintf.cc assert.h wrapper
Date: Thu, 30 May 2024 17:04:01 -0400 (EDT)

Follow-up Comment #7, bug #65811 (group gettext):


> I'm not saying packages should not use gnulib, I'm saying that it would be
helpful if packages would not use an arbitrary commit. Instead, gnulib could
have releases, and backports / patch releases, and it would be nice if
packages could allow an external version.
> 
> The problem for packagers is that bug fixes (and compiler support) for
gnulib have to be patched at the source of tons of release tarballs of
dependents of gnulib, instead of in a the package gnulib itself.

Oh, that's what you meant.

For this purpose, Gnulib now has stable branches, that include bug fixes and
support for new compilers. See
https://www.gnu.org/software/gnulib/manual/html_node/Stable-Branches.html .
However, many packages use a specific gnulib commit rather than a branch,
because they depend on Gnulib features added specifically for their package.

In the simplest case (only changes to .h and .c files needed for the fix) it
is sufficient to patch all copies of these files in the package's tarball.

In the more complicated case that .m4 files changes are needed as well, the
packager will have to run aclocal, autoconf, autoheader, "automake -a -c" as
well.

In the most complicated case that module dependencies change too, the packager
will have to download the relevant revision of Gnulib and run the 'autogen.sh'
/ bootstrap / 'gnulib-tool --update' command, to fetch the changes.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65811>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]