unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: yamaoka@jpl.org, 32352@debbugs.gnu.org, markusffm@fn.de
Subject: bug#32352: 27.0.50; build error
Date: Tue, 13 Nov 2018 08:54:24 -0500	[thread overview]
Message-ID: <87in11gk1b.fsf@gmail.com> (raw)
In-Reply-To: <83pnv98x9l.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Nov 2018 05:35:50 +0200")

tags 32352 fixed
close 32352 
quit

Eli Zaretskii <eliz@gnu.org> writes:

> I see no need to do this on the release branch, especially since a
> pretest of Emacs 26.2 is about to be produced.

Yeah, I there's an easy workaround and we probably won't be changing
files.el all that often on the release branch anyway.  Pushed to master.

[1: 197bf4eaac]: 2018-11-13 08:25:35 -0500
  Fix build fail on files.el change (Bug#32352)
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=197bf4eaac0ed98549f4343a653ba21aac47c855>

>> (although I'm suddenly unable to build it today, I get tons of
>> "undefined reference to X" link errors (including X=main!?)).

> Builds fine for me, FWIW.

I'm not surprised, it looks like some kind of toolchain failure (maybe I
have some selective hard drive corruption?  It's very strange...).





  reply	other threads:[~2018-11-13 13:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03  5:48 bug#32352: 27.0.50; build error Markus FFM
2018-08-03  6:07 ` Katsumi Yamaoka
2018-08-03  6:50   ` Eli Zaretskii
2018-08-03 12:40     ` Noam Postavsky
2018-11-12 19:01       ` Glenn Morris
2018-11-13  1:37         ` Noam Postavsky
2018-11-13  3:35           ` Eli Zaretskii
2018-11-13 13:54             ` Noam Postavsky [this message]
2018-11-13 13:58           ` Noam Postavsky
2018-11-13 18:10           ` Glenn Morris

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=87in11gk1b.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=32352@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=markusffm@fn.de \
    --cc=yamaoka@jpl.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 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).