From: Michael Mauger <mmauger@protonmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Juri Linkov <juri@linkov.net>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Make bootsrap failure -- tab-bar.el
Date: Mon, 21 Oct 2019 20:45:09 +0000 [thread overview]
Message-ID: <cIom8cPhLhgZaJe7X2TXa6zrZ0qSog53dU3YYI65jmD0D3zcVcxy4O_Q8WYZQjpHh0I5Bx-hDAyzyq7FOq83xwgtMhOo6aqjmd2M_Rc4Faw=@protonmail.com> (raw)
In-Reply-To: <83wod4cyrp.fsf@gnu.org>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, October 16, 2019 2:48 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Juri Linkov juri@linkov.net
>
> > Date: Wed, 16 Oct 2019 20:48:05 +0300
> > Cc: "emacs-devel@gnu.org" emacs-devel@gnu.org
> > Now I got exactly the same error when edited and saved the source file
> > tab-bar.el during compilation.
>
"Doctor, doctor! It hurts when I do this!"
> Don't do that.
:D
I'm doing the `git pull' followed by `autogen.sh' and `make bootstrap' and running into the issue; I'm never touching any files in-between. Also I'm not seeing the compiled version of tab-bar in the build tree. It feels like there is some artifact being left around that is skipping the compile of tab-bar. I've got to do a deeper dive into this to figure out where its happening.
I've got a separate checkout of master that I've used the same build script on and was able to build. So at least I have a recent build but that old master branch checkout is still broken.
I'll report back if I find something that could be an issue for others...
--
MICHAEL@MAUGER.COM // FSF and EFF member // GNU Emacs sql.el maintainer
prev parent reply other threads:[~2019-10-21 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 0:55 Make bootsrap failure -- tab-bar.el Michael Mauger
2019-10-14 19:17 ` Juri Linkov
2019-10-16 17:48 ` Juri Linkov
2019-10-16 18:48 ` Eli Zaretskii
2019-10-21 20:45 ` Michael Mauger [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='cIom8cPhLhgZaJe7X2TXa6zrZ0qSog53dU3YYI65jmD0D3zcVcxy4O_Q8WYZQjpHh0I5Bx-hDAyzyq7FOq83xwgtMhOo6aqjmd2M_Rc4Faw=@protonmail.com' \
--to=mmauger@protonmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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).