GNU bug report logs - #33250
26.1.50; Unable to build emacs-26 branch out of tree on fedora 29

Previous Next

Package: emacs;

Reported by: Pierre Téchoueyres <pierre.techoueyres <at> free.fr>

Date: Sat, 3 Nov 2018 14:53:02 UTC

Severity: normal

Tags: moreinfo, notabug

Found in version 26.1.50

Fixed in version 26.2

Done: pierre.techoueyres <at> free.fr (Pierre Téchoueyres)

Bug is archived. No further changes may be made.

Full log


Message #17 received at 33250 <at> debbugs.gnu.org (full text, mbox):

From: pierre.techoueyres <at> free.fr (Pierre Téchoueyres)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 33250 <at> debbugs.gnu.org
Subject: Re: bug#33250: 26.1.50;
 Unable to build emacs-26 branch out of tree on fedora 29
Date: Sat, 03 Nov 2018 18:41:15 +0100
[Message part 1 (text/plain, inline)]
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: pierre.techoueyres <at> free.fr (Pierre Téchoueyres)
>> Cc: 33250 <at> debbugs.gnu.org
>> Date: Sat, 03 Nov 2018 17:30:43 +0100
>> 
>> Eli Zaretskii <eliz <at> 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?
It's clean, and i also re-created the build-26 directory

Here is the result of git status:
[emacs-26.outoftree.org (text/x-org, inline)]
#+BEGIN_VERSE
╭─   ptechoueyres <at> killashandra   ~/Travail/VCS/Emacs/emacs/emacs-26     emacs-26   1   
╰ LC_ALL=C git status
On branch emacs-26
Your branch is behind 'origin/emacs-26' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Untracked files:
  (use "git add <file>..." to include in what will be committed)

        build-26/

nothing added to commit but untracked files present (use "git add" to track)
#+END_VERSE
[Message part 3 (text/plain, inline)]
and before the build I also did a git clean -dfx

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

I don't too, but as it's the only thing that changed ...

This bug report was last modified 6 years and 281 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.