all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: zijianyue <zijianyue@163.com>, 16429@debbugs.gnu.org
Subject: bug#16429: 24.3.50; an issue in mingw making
Date: Wed, 19 Mar 2014 02:26:47 -0400	[thread overview]
Message-ID: <uneh1y4sbc.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <201401131510563598711@163.com>

Juanma Barranquero wrote:

> Is anything else to be done in this report, or can we close it?

It still needs fixing.

The build process should be robust against EMACSDATA (and DOC, PATH, if
they matter) being previously set in the user's environment (and
registry on MS Windows, if possible).

In other words, something like:

export EMACSDATA=/path/to/emacs/21/etc

should not break a subsequent build of Emacs 24.4 in that environment.


The fix is to use EMACSDATA= where appropriate in the Makefiles,
and to change emacs to ignore an empty value. Or to unset EMACSDATA in
the Makefiles.





  parent reply	other threads:[~2014-03-19  6:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  7:11 bug#16429: 24.3.50; an issue in mingw making zijianyue
2014-01-13 16:53 ` Eli Zaretskii
2014-01-14  1:12   ` bug#16429: " zijianyue
2014-01-14  5:01     ` Eli Zaretskii
2014-03-18 21:32       ` Juanma Barranquero
2014-03-19  3:49         ` Eli Zaretskii
2014-03-19  4:00           ` Juanma Barranquero
2014-03-19  6:26         ` Glenn Morris [this message]
2014-04-11  6:55           ` Glenn Morris
2022-04-21 13:37           ` bug#16429: EMACSDATA in the MS Windows registry can interfere with building Lars Ingebrigtsen
2022-04-21 15:26             ` Glenn Morris
2022-05-20  2:15               ` Lars Ingebrigtsen
2022-05-20 14:12                 ` Eli Zaretskii
2014-01-13 17:01 ` bug#16429: 24.3.50; an issue in mingw making Glenn Morris
2014-01-13 17:44   ` Eli Zaretskii

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=uneh1y4sbc.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=16429@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=zijianyue@163.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.
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.