all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: gettext: Enable "xgettext --language=glade"
Date: Mon, 18 Nov 2013 00:19:24 +0100	[thread overview]
Message-ID: <877gc639c3.fsf@gnu.org> (raw)
In-Reply-To: <20131117122546.GA32131@debian> (Andreas Enge's message of "Sun, 17 Nov 2013 13:25:46 +0100")

Andreas Enge <andreas@enge.fr> skribis:

>       `(#:phases (alist-cons-before
> +                 'configure 'link-expat
> +                 (lambda _
> +                   (substitute* "gettext-tools/configure"
> +                     (("LIBEXPAT=\"-ldl\"") "LIBEXPAT=\"-ldl -lexpat\"")
> +                     (("LTLIBEXPAT=\"-ldl\"") "LTLIBEXPAT=\"-ldl -lexpat\"")))

Actually, it seems to be solvable without adding the dependency:

--8<---------------cut here---------------start------------->8---
$ xgettext -L glade /dev/null 
xgettext: Language "glade" is not supported. xgettext relies on expat.
          This version was built without expat.

$ LD_LIBRARY_PATH=$(guix build expat)/lib xgettext -L glade /dev/null 
xgettext: /dev/null:1:1: no element found
--8<---------------cut here---------------end--------------->8---

(The error message is misleading because it’s not a build-time issue.)

Would it work for you to just use that LD_LIBRARY_PATH trick where it’s
needed?

That way we avoid making gettext “fatter”.  I suppose we’ll seldom need
to do that trick anyway.

WDYT?

Ludo’.

  parent reply	other threads:[~2013-11-17 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17 12:25 [PATCH] gnu: gettext: Enable "xgettext --language=glade" Andreas Enge
2013-11-17 21:00 ` Ludovic Courtès
2013-11-17 23:19 ` Ludovic Courtès [this message]
2013-11-18  8:17   ` Andreas Enge
2013-11-18  9:17     ` Ludovic Courtès
2013-11-18  9:58       ` Andreas Enge
2013-11-18 10:05         ` Andreas Enge
2013-11-18 12:58         ` Ludovic Courtès

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=877gc639c3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.