all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66125@debbugs.gnu.org
Subject: bug#66125: 29.1; configure --with-small-ja-dic has no effect
Date: Sat, 23 Sep 2023 23:29:33 +0200	[thread overview]
Message-ID: <uwmwg60jm@gentoo.org> (raw)
In-Reply-To: <83o7ht3vy5.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 23 Sep 2023 15:39:30 +0300")

>>>>> On Sat, 23 Sep 2023, Eli Zaretskii wrote:

>> > (The "if test" part of the new target's rules could be updated to
>> > check that the small-ja-dic-option file exists, and generate a
>> > non-empty file if not.)
>> 
>> IMHO this would be cleaner.

> Can you try that and see if there are no other issues?

I did some tests and ended up replacing the small-ja-dic-option recipe
in leim/Makefile.in with something very simple:

# This is used to support regeneration of ja-dic when the SMALL_JA_DIC
# option is flipped by the configure-time option.
small-ja-dic-option: ../config.status
	$(AM_V_GEN)echo "small ja-dic option: $(SMALL_JA_DIC)" > $@.$$$$ && \
	${top_srcdir}/build-aux/move-if-change $@.$$$$ $@

AFAICS this does what is intended, i.e. the detour via recording the
option in ja-dic.el isn't even needed.





  reply	other threads:[~2023-09-23 21:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 16:16 bug#66125: 29.1; configure --with-small-ja-dic has no effect Ulrich Mueller
2023-09-20 16:27 ` Eli Zaretskii
2023-09-20 16:58   ` Ulrich Mueller
2023-09-20 17:02     ` Eli Zaretskii
2023-09-20 18:21       ` Ulrich Mueller
2023-09-20 18:54         ` Eli Zaretskii
2023-09-23  7:55       ` Eli Zaretskii
2023-09-23  9:15         ` Ulrich Mueller
2023-09-23  9:35           ` Eli Zaretskii
2023-09-23 11:30             ` Ulrich Mueller
2023-09-23 12:39               ` Eli Zaretskii
2023-09-23 21:29                 ` Ulrich Mueller [this message]
2023-09-24 12:33                   ` Eli Zaretskii
2023-09-24 14:57                     ` Ulrich Mueller

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=uwmwg60jm@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=66125@debbugs.gnu.org \
    --cc=eliz@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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.