unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: build problem with git worktree linked to main worktree (repo) (was: strange build problem with missing -by.el and -wy.el files)
Date: Sun, 06 Nov 2022 00:46:18 +0100	[thread overview]
Message-ID: <87iljt2cdx.fsf@no.workgroup> (raw)

Hi Eli, emacs users,
* Eli Zaretskii <eliz@gnu.org> [2022-11-01; 18:48 +02]:
>> From: Gregor Zattler <telegraph@gmx.net>
>> Date: Tue, 01 Nov 2022 16:38:53 +0100
>>
>> > You need to understand why c-by.el is not generated as part of the
>> > build.  It's supposed to be generated by the rules in
>> > admin/grammars/Makefile.in, which run early on during the build.  It
>> > is run via the rule in lisp/Makefile.in for the target "semantic",
>> > look around line 415 in that file.  Why doesn't that happen in your
>> > case?
>>
>> Because I get "Args out of range: "master", 0, 7"
>> errors when building these files:
>
> So you need to understand why this happens.

I do not understand why this happens.

> Perhaps some stale files from previous builds, or some
> other problem?

This is from pristine sources.

But I found how to avoid it: Not using a git worktree linked
to a main worktree with .git directory:

The problem arises when the tree from which to build Emacs
is actually a linked git worktree as opposed to a fully
fletched git repo (main worktree in git parlance).

Building in a linked worktree linked to a bare repo works
without problems, though.

I described my findings in bug#59064.

I now will use git worktrees linked to a bare repo.

Thanks to Eli fro the hints, Gregor




             reply	other threads:[~2022-11-05 23:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 23:46 Gregor Zattler [this message]
2022-11-06  3:59 ` build problem with git worktree linked to main worktree (repo) Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-06 21:30   ` Gregor Zattler

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=87iljt2cdx.fsf@no.workgroup \
    --to=telegraph@gmx.net \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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.
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).