Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: "'Todd Zullinger'" <tmz@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: [ANNOUNCE] Git v2.41.0-rc2
Date: Thu, 25 May 2023 10:48:17 -0400	[thread overview]
Message-ID: <025c01d98f17$f4b3bca0$de1b35e0$@nexbridge.com> (raw)
In-Reply-To: <ZG6gbN04DfldoadD@pobox.com>

On Wednesday, May 24, 2023 7:40 PM, Todd Zullinger wrote:
>rsbecker@nexbridge.com wrote:
>> I'm not sure this is a new thing but it is the first time I noticed it
>> in the log. It was not in the build log for 2.41.0-rc0.
>>
>> /usr/coreutils/bin/bash: line 3: tclsh: command not found
>>     * tclsh failed; using unoptimized loading
>
>Have you set NO_TCLTK in your builds?  I don't see that in the NonStop
section of
>config.mak.uname.
>
>> Tclsh is not available on NonStop or S/390 AFAIK. While its use does
>> go back to 2007, I just want to ensure that it does not sneak in as a
>> dependency beyond git-gui and gitk-git.
>
>The only references to tclsh outside of the Makefile and git-gui/gitk are
commented
>code in contrib/buildsystems/, engine.pl and parse.pl.

Setting NO_TCLTK=NoThanks inhibits processing of some .po files. I do not
know whether that is intended. Can you advise

Thanks,
Randall


  parent reply	other threads:[~2023-05-25 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 21:41 [ANNOUNCE] Git v2.41.0-rc2 Junio C Hamano
2023-05-24 23:06 ` rsbecker
2023-05-24 23:40   ` Todd Zullinger
2023-05-25 13:56     ` rsbecker
2023-05-25 14:48     ` rsbecker [this message]
2023-05-25 16:38       ` 'Todd Zullinger'
2023-05-25 17:26         ` rsbecker
2023-05-25 17:39           ` 'Todd Zullinger'
2023-05-25 17:48             ` 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='025c01d98f17$f4b3bca0$de1b35e0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=git@vger.kernel.org \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).