unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: 28.1: errors about missing git executable
Date: Sat, 09 Apr 2022 10:09:54 +0300	[thread overview]
Message-ID: <8335imag1p.fsf@gnu.org> (raw)
In-Reply-To: <87a6cvei6j.fsf@telefonica.net> (message from Óscar Fuentes on Fri, 08 Apr 2022 16:57:56 +0200)

> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Fri, 08 Apr 2022 16:57:56 +0200
> 
> While building 28.1 from the source tar package I see lots of mentions
> to missing git:
> 
>     ELN  ../../emacs-28.1/lisp/tooltip.eln
>     ELN  ../../emacs-28.1/lisp/uniquify.eln
>   Error: (file-missing "Searching for program" "No such file or directory" "git")
>   Error: (file-missing "Searching for program" "No such file or directory" "git")
> 
> ...
> 
> 
>   Loading leim/leim-list.el (source)...
>   Waiting for git...
>   Error running git rev-parse: (file-missing "Searching for program" "No such file or directory" "git")
>   Waiting for git...
>   Error running git rev-parse --abbrev-ref: (file-missing "Searching for program" "No such file or directory" "git")
>   Finding pointers to doc strings...
> 
> The build goes along, but I wonder why those messages are shown and if
> they have an effect on the build products.

The last two messages (about git rev-parse) are harmless (they are
inside ignore-errors), but those emitted by ELN are not expected, I
think.  A Lisp backtrace for those errors should be useful.

Actually, a full-fledged bug report with all the details, including
how you configured the build, would be appreciated.



      reply	other threads:[~2022-04-09  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 14:57 28.1: errors about missing git executable Óscar Fuentes
2022-04-09  7:09 ` 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=8335imag1p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    /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).