git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>, Johannes Sixt <j6t@kdbg.org>
Cc: rsbecker@nexbridge.com,  git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.50.0-rc1 - Test Failed
Date: Wed, 04 Jun 2025 08:17:31 -0700	[thread overview]
Message-ID: <xmqqjz5rcz90.fsf@gitster.g> (raw)
In-Reply-To: <aEBPdFXpIca7lMls@teonanacatl.net> (Todd Zullinger's message of "Wed, 4 Jun 2025 09:51:48 -0400")

Todd Zullinger <tmz@pobox.com> writes:

> rsbecker@nexbridge.com wrote:
>>>I hit a new issue during the test phase.
>>>
>>>Makefile:200: recipe for target 'lib/tclIndex' failed
>>>
>>>Is there any way to suppress this? I don't think we need TCL - don't have it anyway
>>>on NonStop.
>> 
>> More info:
>> 
>> The actual more complete error is:
>> 
>> /usr/coreutils/bin/bash generate-git-gui.sh "git-gui.sh" "git-gui" ./GIT-GUI-BUILD-OPTIONS ./GIT-VERSION-FILE
>> /usr/coreutils/bin/bash generate-tclindex.sh . ./GIT-GUI-BUILD-OPTIONS 
>> usage: generate-tclindex.sh <BUILD_DIR> <BUILD_OPTIONS> <LIBFILE> [<LIBFILE>...]
>> Makefile:200: recipe for target 'lib/tclIndex' failed
>> 
>> This seems like a legit problem to be fixed rather than ignored.
>
> If you don't have TCL, are you not setting NO_TCLTK for your
> builds?
>
> I don't think that's changed in ages, but perhaps something
> has changed in the build process or your build system which
> now exposes that you aren't setting it, which then tries to
> build git-gui (and would surely try to build gitk as well).

Curious.

$ git diff --name-status v2.50.0-rc0 v2.50.0-rc1 -- git-gui/ gitk-git/
M	git-gui/.gitattributes
M	git-gui/.gitignore
A	git-gui/GIT-GUI-BUILD-OPTIONS.in
M	git-gui/GIT-VERSION-GEN
M	git-gui/Makefile
A	git-gui/generate-git-gui.sh
A	git-gui/generate-macos-app.sh
A	git-gui/generate-macos-wrapper.sh
A	git-gui/generate-tclindex.sh
A	git-gui/lib/meson.build
A	git-gui/meson.build
A	git-gui/po/meson.build
M	gitk-git/Makefile
M	gitk-git/gitk
$ git diff --stat v2.50.0-rc0 v2.50.0-rc1 -- git-gui/ gitk-git/
 git-gui/.gitattributes            |   1 +
 git-gui/.gitignore                |   2 +-
 git-gui/GIT-GUI-BUILD-OPTIONS.in  |   7 ++
 git-gui/GIT-VERSION-GEN           |  44 ++++++++----
 git-gui/Makefile                  | 115 ++++++++---------------------
 git-gui/generate-git-gui.sh       |  29 ++++++++
 git-gui/generate-macos-app.sh     |  30 ++++++++
 git-gui/generate-macos-wrapper.sh |  35 +++++++++
 git-gui/generate-tclindex.sh      |  32 +++++++++
 git-gui/lib/meson.build           |  74 +++++++++++++++++++
 git-gui/meson.build               | 148 ++++++++++++++++++++++++++++++++++++++
 git-gui/po/meson.build            |  38 ++++++++++
 gitk-git/Makefile                 |   2 +-
 gitk-git/gitk                     |  10 ++-
 14 files changed, 458 insertions(+), 109 deletions(-)

So the build procedure for git-gui (but not gitk) has changed rather
extensively after we tagged the preview before -rc1?  Honestly, I
would have preferred to see a change with this impact go through the
regular 'seen' to 'next' to 'master' way before -rc0, but that is
water under the bridge.

We are in an exciting cycle X-<.

J6t?

I do not spot anything obviously wrong (and it is not expected that
I would---we wouldn't have this code sent to me in the first place
if this is something I can immediately notice).  git-gui/Makefile
sets ALL_LIBFILES to $(wildcard lib/*.tcl) and then does

    $(SHELL_PATH) generate-tclindex.sh . ./GIT-GUI-BUILD-OPTIONS $(ALL_LIBFILES)

So the error message in Becker's message, i.e.

> /usr/coreutils/bin/bash generate-tclindex.sh . ./GIT-GUI-BUILD-OPTIONS 
> usage: generate-tclindex.sh <BUILD_DIR> <BUILD_OPTIONS> <LIBFILE> [<LIBFILE>...]
> Makefile:200: recipe for target 'lib/tclIndex' failed

suggests that $(wildcard lib/*tcl) expanded to *nothing*, which
sounds horribly wrong.  They are source material and should exist in
an unmodified checkout or a tarball extract.


  reply	other threads:[~2025-06-04 15:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 17:02 [ANNOUNCE] Git v2.50.0-rc1 Junio C Hamano
2025-06-03 22:33 ` [ANNOUNCE] Git v2.50.0-rc1 - Test Failed rsbecker
2025-06-03 22:45   ` rsbecker
2025-06-04 13:51     ` Todd Zullinger
2025-06-04 15:17       ` Junio C Hamano [this message]
2025-06-04 19:25         ` Johannes Sixt
2025-06-05  8:09           ` rsbecker
2025-06-05  8:56             ` Patrick Steinhardt
2025-06-05 20:27               ` rsbecker
2025-06-05 21:11                 ` Johannes Sixt
2025-06-05 21:33                   ` Junio C Hamano
2025-06-06  5:57                     ` [GIT PULL] git-gui: fix for: " Johannes Sixt
2025-07-22 17:45                     ` [GIT PULL] git-gui: Sync with 2.50.1, Tcl >= 8.6, git >= 2.36 Johannes Sixt
2025-06-05 21:44                   ` [ANNOUNCE] Git v2.50.0-rc1 - Test Failed rsbecker
2025-06-05 22:06                     ` Junio C Hamano
2025-06-05 23:38                       ` 'Todd Zullinger'
2025-06-06  7:20                         ` rsbecker

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=xmqqjz5rcz90.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.org \
    --cc=rsbecker@nexbridge.com \
    --cc=tmz@pobox.com \
    /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 NNTP newsgroup(s).