unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Build failure caused by a .tit file
Date: Tue, 18 Apr 2017 19:39:30 +0300	[thread overview]
Message-ID: <83lgqxd60t.fsf@gnu.org> (raw)
In-Reply-To: <87wpahadsg.fsf@gkayaalp.com> (message from Göktuğ Kayaalp on Tue, 18 Apr 2017 19:19:59 +0300)

> From: Göktuğ Kayaalp <self@gkayaalp.com>
> Cc: help-gnu-emacs@gnu.org
> Date: Tue, 18 Apr 2017 19:19:59 +0300
> 
> > If it does exist, do you have EMACSDATA or EMACSPATH variables set in
> > the environment?  Do you run Emacs from a shell or from inside another
> > Emacs session?
> 
> Within a shell within Emacs.  Those variables are not set.

Try from a shell outside Emacs.

> Responding also to the other message of yours, my local copy of the repo
> does not contain any extraneous files I know of, I just update it via
> ‘git pull’ every now and then.  I have a branch that I build my stable
> versions from, but this troublesome build is on master.

What does "git status" say in the repo where you build?

One more thing to try: remove all the *.elc files in the source tree,
and try building again.

> > (And why are we still discussing this on help-gnu-emacs?)
> 
> I'll retry on the weekend from a pristine copy of the repo that I'll
> fetch from the upsteam, and report the results.  Should I switch to
> emacs-devel?

No, please use "M-x report-emacs-bug RET", which will send the report
to the bug tracker and also to the bug-gnu-emacs mailing list.  Then
let's take it from there (assuming building a fresh clone still
crashes or errors out).  The right place to discuss Emacs bugs is via
the bug tracker.  All the core maintainers subscribe to the bug list.

Thanks.



      reply	other threads:[~2017-04-18 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 14:03 Build failure caused by a .tit file Göktuğ Kayaalp
2017-04-17 14:41 ` 良ϖ
2017-04-17 15:57   ` Göktuğ Kayaalp
2017-04-17 14:45 ` Eli Zaretskii
2017-04-17 15:55   ` Göktuğ Kayaalp
2017-04-17 16:21     ` Eli Zaretskii
2017-04-17 23:08       ` Göktuğ Kayaalp
2017-04-18  2:43         ` Eli Zaretskii
2017-04-18 12:41           ` Göktuğ Kayaalp
2017-04-18 13:16             ` Göktuğ Kayaalp
2017-04-18 15:02               ` Eli Zaretskii
2017-04-18 14:56             ` Eli Zaretskii
2017-04-18 16:19               ` Göktuğ Kayaalp
2017-04-18 16:39                 ` 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=83lgqxd60t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).