Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Remove LIBINTL_DEP
Date: Thu, 20 Jun 2024 21:13:37 +0930	[thread overview]
Message-ID: <ZnQV6c1zByruwACm@squeak.grove.modra.org> (raw)
In-Reply-To: <87zfrggdtx.fsf@aarsen.me>

On Thu, Jun 20, 2024 at 11:31:38AM +0200, Arsen Arsenović wrote:
> Hi Alan,
> 
> Alan Modra <amodra@gmail.com> writes:
> 
> > The intl directory in the source no longer exists.  LIBINTL_DEP is
> > thus always empty.  Remove references to it.
> 
> That's not the case, though - it can be populated by gettext-runtimes
> uninstalled-config.sh via ZW_GNU_GETTEXT_SISTER_DIR.

Oh.

> Are you sure the build still works unchanged without this variable?
> Could you try configuring with in-tree gettext 0.22 or later to check if
> it still works and the proper dependencies are emitted?  I suspect they
> won't be, but that the build will work due to the toplevel dependencies.

It works for me, but that's likely because my uninstalled-config.sh
has

if test no = yes; then
  LIBINTL_DEP="${relative_builddir}/intl/libintl.la"
else
  LIBINTL_DEP=
fi

Hmm, seems I need to configure using --with-included-gettext, and then
the opcodes compile fails because I took LIBINTL out of BUILD_LIBS.
Putting it back in succeeds but if you are building intl in tree then
you really ought to have LIBINTL_DEP.

So the patch is just plain wrong.  Reverting.

-- 
Alan Modra

  reply	other threads:[~2024-06-20 11:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20  9:04 Alan Modra
2024-06-20  9:31 ` Arsen Arsenović
2024-06-20 11:43   ` Alan Modra [this message]
2024-06-20 11:12 ` Mark Wielaard
2024-06-20 11:50   ` Alan Modra
2024-06-20 16:51     ` Mark Wielaard
2024-06-20 20:02       ` Andreas Schwab

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=ZnQV6c1zByruwACm@squeak.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=arsen@aarsen.me \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    /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