From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: zijianyue@163.com, 16429@debbugs.gnu.org
Subject: bug#16429: 24.3.50; an issue in mingw making
Date: Mon, 13 Jan 2014 19:44:35 +0200 [thread overview]
Message-ID: <831u0b7p4s.fsf@gnu.org> (raw)
In-Reply-To: <t9sisrolxo.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Mon, 13 Jan 2014 12:01:39 -0500
> Cc: 16429@debbugs.gnu.org
>
> Note that you have the following environment variables set.
They could be either in the environment or in the Registry. If
neither of these is set, we will not see these variables in the bug
report.
> There's no need to have these set (unless you want to do something
> unusual), and setting them is a great way to break Emacs in exactly the
> way you seem to describe above.
Right.
> So try unsetting them before you build.
If they are in the Registry, they should be deleted with regedit.
> The build process should probably unset EMACSDATA (and DOC?), like it
> does with EMACSLOADPATH.
Not sure whether we care about EMACSDOC during the build.
> I guess EMACSPATH doesn't matter?
I don't think it does.
prev parent reply other threads:[~2014-01-13 17:44 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831u0b7p4s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16429@debbugs.gnu.org \
--cc=rgm@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).