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

> From: Ulrich Mueller <ulm@gentoo.org>
> Cc: 66125@debbugs.gnu.org
> Date: Sat, 23 Sep 2023 13:30:36 +0200
> 
> >> Hm, this creates an empty leim/small-ja-dic-option file after the first
> >> round of configure+make:
> 
> > That's a one-time issue.  I didn't think it was worth extra hassle to
> > avoid that.  Do you see any problem with that?
> 
> Not sure. Is it guaranteed that the empty file won't be included in the
> release tarball?
> 
> > (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?





  reply	other threads:[~2023-09-23 12:39 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 [this message]
2023-09-23 21:29                 ` Ulrich Mueller
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=83o7ht3vy5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66125@debbugs.gnu.org \
    --cc=ulm@gentoo.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.