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: Harmen
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 12:55:18 -0400 (EDT)

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


>  So, it seems that the failure is caused by the '-std=gnu++11' flag, and
this flag is not being added by the autoconfiguration, but rather you must
have been specifying it through the CXX variable. 

It's added by the configure script of `gettext-runtime/libasprintf`:

```
checking for /path/to/g++ option to enable C++11 features... -std=gnu++11
```

Everything is fine with GCC 6 and above. Are you sure you tried with GCC 4.8.5
/ 5.5.0?

The default compiler on CentOS 7 is 4.8.5. On Ubuntu 18.04 you need `apt
install g++-5 gcc-5`, system compiler is GCC 7.

>  Then so many GNU packages would waste time reinventing the wheel. Which is
not desirable. 

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.

But anyways, that is unrelated to this issue.


    _______________________________________________________

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]