all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: pierre.techoueyres@free.fr (Pierre Téchoueyres)
Cc: 33250@debbugs.gnu.org
Subject: bug#33250: 26.1.50; Unable to build emacs-26 branch out of tree on fedora 29
Date: Sat, 03 Nov 2018 18:59:28 +0200	[thread overview]
Message-ID: <83r2g2drm7.fsf@gnu.org> (raw)
In-Reply-To: <878t2aw2bw.fsf@killashandra.ballybran.fr> (pierre.techoueyres@free.fr)

> From: pierre.techoueyres@free.fr (Pierre Téchoueyres)
> Cc: 33250@debbugs.gnu.org
> Date: Sat, 03 Nov 2018 17:30:43 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> I'm attaching the trace file of compilation output.
> >> [...]
> >>   GEN      ../etc/DOC
> >> loaddefs.el: No such file or directory
> >> make[1]: *** [Makefile:559: ../etc/DOC] Error 1
> >
> > I think the above is the root cause.  Where's loaddefs.el being
> > generated?
> >
> 
> I'm unable to find the file.
> I tried with the following command:
> find . -iname loaddefs.el in my ~/Travail/VCS/Emacs/emacs/emacs-26  directory
> It seems the generation of this file has failed.

Then Emacs should have loaded ldefs-boot.el instead, and I see in your
trace that it did.

Is your source tree clean?  Or was it used for another in-tree build?

Anyway, I cannot see what all this could have with your OS update.





  reply	other threads:[~2018-11-03 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-03 14:51 bug#33250: 26.1.50; Unable to build emacs-26 branch out of tree on fedora 29 Pierre Téchoueyres
2018-11-03 16:08 ` Eli Zaretskii
2018-11-03 16:30   ` Pierre Téchoueyres
2018-11-03 16:59     ` Eli Zaretskii [this message]
2018-11-03 17:41       ` Pierre Téchoueyres
2018-11-05 18:37 ` Paul Eggert
2018-11-07 22:55   ` Pierre Téchoueyres
2018-11-07 23:29     ` Paul Eggert
2018-11-09  0:35       ` Pierre Téchoueyres

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=83r2g2drm7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33250@debbugs.gnu.org \
    --cc=pierre.techoueyres@free.fr \
    /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.