public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iain@sandoe.co.uk>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Arsen Arsenović" <arsen@aarsen.me>,
	"Bruno Haible" <bruno@clisp.org>,
	"GDB Patches" <gdb-patches@sourceware.org>,
	"GCC Binutils" <binutils@sourceware.org>
Subject: Re: [PATCH v2 1/2] *: add modern gettext support
Date: Tue, 26 Sep 2023 08:54:10 +0100	[thread overview]
Message-ID: <B2D49E73-76E6-45D4-B176-98E282590E9A@sandoe.co.uk> (raw)
In-Reply-To: <1c90c3ea-0b54-520c-8524-7feb6b88212e@suse.com>

Hi Jan,

> On 26 Sep 2023, at 08:03, Jan Beulich <jbeulich@suse.com> wrote:
> 
> On 26.09.2023 02:17, Arsen Arsenović via Binutils wrote:
>> ChangeLog:
>> 
>> 	* .gitignore: Add '/gettext*'.
>> 	* configure.ac (host_libs): Replace intl with gettext.
>> 	(hbaseargs, bbaseargs, baseargs): Split baseargs into {h,b}baseargs.
>> 	(skip_barg): New flag.  Skips appending current flag to bbaseargs.
>> 	<library exemptions>: Exempt --with-libintl-{type,prefix} from
>> 	target and build machine argument passing.
>> 	* configure: Regenerate.
>> 	* Makefile.def (host_modules): Replace intl module with gettext
>> 	module.
>> 	(configure-ld): Depend on configure-gettext.
>> 	* Makefile.in: Regenerate.
>> 
>> config/ChangeLog:
>> 
>> 	* intlmacosx.m4: Import from gettext-0.22 (serial 8).
>> 	* gettext.m4: Sync with gettext-0.22 (serial 77).
>> 	* gettext-sister.m4 (ZW_GNU_GETTEXT_SISTER_DIR): Load gettext's
>> 	uninstalled-config.sh, or call AM_GNU_GETTEXT if missing.
>> 	* iconv.m4: Sync with gettext-0.22 (serial 26).
>> 
>> gas/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* configure: Regenerate.
>> 
>> gold/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* configure: Regenerate.
>> 
>> gprof/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* configure: Regenerate.
>> 
>> ld/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* configure: Regenerate.
>> 
>> libctf/ChangeLog:
>> 
>> 	* Makefile.am (SUBDIRS): Define to empty to suppress a check in
>> 	Automake.
>> 	* Makefile.in: Regenerate.
>> 	* configure.ac (CTF_LIBADD): Use LTLIBINTL rather than LIBINTL.
>> 	* aclocal.m4: Regenerate.
>> 	* configure: Regenerate.
>> 
>> opcodes/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
>> 	temporary file to suppress xgettext checking charset names.
>> 	* configure.ac (SHARED_LIBADD): Use LTLIBINTL rather than LIBINTL.
>> 	* configure: Regenerate.
>> 
>> bfd/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* configure.ac (SHARED_LIBADD): Use LTLIBINTL rather than LIBINTL.
>> 	* configure: Regenerate.
>> 
>> binutils/ChangeLog:
>> 
>> 	* aclocal.m4: Regenerate.
>> 	* configure: Regenerate.
> 
> May I please ask that a change like this come with a real description? The
> ChangeLog entries certainly describe - purely mechanically - what is done
> to the files, but to be honest I cannot really read out of the (large)
> patch what the overall behavioral change is. I'm therefore only getting
> the impression that you make gettext 0.22(?) a prereq to building binutils
> and gdb.

I’ll leave to Arsen to expand upon this ^

> Which in turn may make it impossible to (easily) build either on
> older systems (it would certainly limit [remove?] my ability to test 32-bit
> builds of binutils, as the newer distros I use all only come in 64-bit
> flavors; there may be ways to configure as 32-bit, but past experience has
> shown that such is potentially fragile / only partially functioning).

I have one datum at least:

In this context, gettext is a host library, so the concern is about the oldest,
least capable, hosts you might wish to support.

* AFAIU, if your host already has libintl installed you do not need to do
anything (unless you happen to want a newer version).

* My oldest (regularly-tested) 32b host is Darwin9 (2007):
 - it has no installed libintl
 - it is not even ELF.

Here:
 * if I do nothing, binutils builds without NLS support.
 * If I symlink (or copy) gettext 0.22 into the root source dir then it builds
along with the other sources and I get NLS support.

HTH (at least as some reassurance that we have tested in older environments)
Iain

$ LANG=ja_JP /opt/iains/i686-apple-darwin9/binutils-gdb-master/bin/objdump fff
使用法: /opt/iains/i686-apple-darwin9/binutils-gdb-master/bin/objdump <option(s)> <file(s)>
 オブジェクトファイル <file(s)> の情報を表示する
 下記のスイッチの中で最低一つは指定しなければいけません:




  reply	other threads:[~2023-09-26  7:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26  0:17 [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-26  0:17 ` [PATCH v2 1/2] *: add modern gettext support Arsen Arsenović
2023-09-26  2:12   ` Kevin Buettner
2023-09-26  7:03   ` Jan Beulich
2023-09-26  7:54     ` Iain Sandoe [this message]
2023-09-26 14:44     ` Arsen Arsenović
2023-09-27  7:11       ` Jan Beulich
2023-09-27 13:06         ` Arsen Arsenović
2023-09-27 15:19         ` Nick Clifton
2023-09-27 17:43           ` Arsen Arsenović
2023-09-28  9:43             ` Nick Clifton
2023-09-29 15:58       ` Bruno Haible
2023-09-29 16:27         ` Arsen Arsenović
2023-11-20 16:42   ` Kévin Le Gouguec
2023-11-20 20:30     ` Arsen Arsenović
2023-11-20 21:28       ` Bruno Haible
2023-09-26  0:17 ` [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-27 15:21   ` Nick Clifton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B2D49E73-76E6-45D4-B176-98E282590E9A@sandoe.co.uk \
    --to=iain@sandoe.co.uk \
    --cc=arsen@aarsen.me \
    --cc=binutils@sourceware.org \
    --cc=bruno@clisp.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jbeulich@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).