Re: [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext

Arsen Arsenović wrote: > -+The in-tree configuration requires GNU gettext v0.22. Can you change this to "... requires GNU gettext version 0.22 or newer.", please? I wouldn't like to give the impression that a particular release (0.22) is the only one that works. Also, some people may understand '

Re: [PATCH 0/2] Replace intl/ with out-of-tree GNU gettext

Arsen Arsenović wrote: > Do you like the following? > > @@ -486,7 +486,7 @@ found in a subdirectory of your GCC sources > will be built together with GCC, unless present in the system (either in > libc or as a stand-alone library). > > -The in-tree configuration requires GNU gettext v0.22. > +

Re: [PATCH v2 2/2] *: add modern gettext

Arsen Arsenović wrote: > * intlmacosx.m4: Import from gettext-0.22 (serial 8). A further suggestion (can be done in a separate patch, later): Use intlmacosx.m4 from gettext-0.22.3 (serial 9). This version enables portability to macOS 14, which was released on 2023-09-26. (Older versions

[PATCH] Extend --with-zstd documentation

The patch that was so far added for documenting --with-zstd is pretty minimal: - it refers to undocumented options --with-zstd-include and --with-zstd-lib; - it suggests that --with-zstd can be used without an argument; - it does not clarify how this option applies to cross-compilation.

Re: building GNU gettext on AIX

[CCing bug-gettext] David Edelsohn wrote in : > The current gettext-0.22.3 fails to build for me on AIX. Here are some hints to get a successful build of GNU gettext on AIX: 1. Set the recommended environment variables before r

Re: building GNU gettext on AIX

David Edelsohn wrote: > When I try to configure gettext-0.22.3, I receive the following error: > > checking for socklen_t equivalent... configure: error: Cannot find a type > to use in place of socklen_t > > configure: error: > /nasfarm/edelsohn/src/gettext-0.22.3/libtextstyle/configure failed fo

Re: building GNU gettext on AIX

David Edelsohn wrote: > I am using my own install of GCC for a reason. I have built GNU gettext 0.22.3 in various configurations on the AIX 7.1 and 7.3 machines in the compilefarm, and haven't encountered issues with 'max_align_t' nor with 'getpeername'. So, from my point of view, GNU gettext work

Re: building GNU gettext on AIX

David Edelsohn wrote: > > It is great that gettext and libintl can be built thread-safe, but GCC > > (cc1, gcov, etc.) are not pthreads applications and are not built with > > pthreads. Because libintl defaults to pthreads enabled, NLS cannot > > function in GCC on AIX by default. > ... > The la

Re: building GNU gettext on AIX

David Edelsohn wrote: > I manually commented out HAVE_PTHREAD_API from config.h and produced a > libintl.a without references to pthreads. Good finding! Commenting out HAVE_PTHREAD_API from config.h is also what makes the option --enable-threads=isoc work as expected on AIX 7.3. Bruno

Re: building GNU gettext on AIX

Arsen Arsenović wrote: > > * If yes, then the question is how distributors will in general package > > libintl on AIX. If it's installed in public locations (such as in > > /opt/freeware/{lib,lib64}/libintl.a on gcc119.fsffrance.org), then we > > have a problem: It may cause undefined

Re: building GNU gettext on AIX

Hi David, > the default, distributed libintl library will not allow GCC to be built > with NLS enabled. The problem is this configure test from gettext.m4 checking for GNU gettext in libintl... no It should say checking for GNU gettext in libintl... yes I reproduce it with simple hello-wo

Re: building GNU gettext on AIX

David Edelsohn wrote: > > ibm-clang links against libpthread.a as well: > > $ ldd /opt/IBM/openxlC/17.1.1/bin/.ibm-clang.orig > > /opt/IBM/openxlC/17.1.1/bin/.ibm-clang.orig needs: > > /usr/lib/libpthreads.a(shr_xpg5_64.o) > > /usr/opt/zlibNX/lib/libz.a(libz.so.1) > >

Re: building GNU gettext on AIX

David Edelsohn and Richard Biener wrote: > > > * GCC can pass --enable-threads=isoc, to avoid the libpthread dependency > > > on AIX ≥ 7.2. > > > > Hmm, would that option work everywhere, though? Or would we have to > > wire up configury to detect which flag to use? If so, what would it > >

Re: building GNU gettext on AIX

I wrote in : > > The latest issue is that a few files in gettext ignore --disable-pthreads > > and creates a dependency on pthread_mutex. > ... > * If no, then the simple solution would be to pass the configure option > --

Re: [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext

David Edelsohn wrote: > --disable-threads currently does not completely disable threads. Bruno is > suggesting --enable-threads=isoc that relies on mtx mutex functions in libc. Unfortunately, as said in the other mail today, relying only on mtx_* functions did not drop the dependency towards libp

Re: [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext

I wrote: > you (Arsen) should state in the documentation > (gcc/doc/install.texi) that for --disable-threads to have this effect, > one needs gettext version 0.22.4 or newer. Not in gcc/doc/install.texi, but elsewhere. This topic is not relevant to the average user who installs GCC from a tarball

Re: [PATCH v3 0/2] Replace intl/ with out-of-tree GNU gettext

Arsen Arsenović wrote: > Comparing stages 2 and 3 > Bootstrap comparison failure! > gettext/libasprintf/autosprintf.o differs > make[2]: *** [Makefile:23435: compare] Error 1 You should be able to work around this by passing the additional option --disable-libasprintf to gettext-runtime/co