Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Fabio Frumento <frumento.fabio@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Built Git 2.27.0 from sources on macOS Catalina fails on "make profile"
Date: Wed, 1 Jul 2020 12:10:18 -0400	[thread overview]
Message-ID: <20200701161018.GD6726@coredump.intra.peff.net> (raw)
In-Reply-To: <E9210645-66F4-4B76-BB26-C8282AE23B3D@gmail.com>

On Wed, Jul 01, 2020 at 06:00:49PM +0200, Fabio Frumento wrote:

> I get several messages like this
> 
> LLVM Profile Warning: Unable to track new values: Running out of static counters.  Consider using option -mllvm -vp-counters-per-site=<n> to allocate more value profile counters at compile time.

That could be related. I don't know enough about llvm's profiling to
say. If it's just a warning and not terminating the process, that might
be OK. But some of the tests check the stderr from Git. If the profiled
binaries are producing extra messages, that could cause a problem (and
it looks like t0410.15 that you posted does make sure stderr is empty,
so this seems a likely culprit).

> I’ve checked the scripts in the t folder, they use #!/bin/sh while
> I’m using zsh could  it be of some relevance? Which shell are they
> supposed to be run?

They're generally run with whatever $SHELL_PATH is set by the Makefile
knobs, which defaults to /bin/sh. The interactive shell you're using
shouldn't be relevant.

-Peff

  reply	other threads:[~2020-07-01 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 13:17 Built Git 2.27.0 from sources on macOS Catalina fails on "make profile" Fabio Frumento
2020-07-01 15:37 ` Jeff King
2020-07-01 16:00   ` Fabio Frumento
2020-07-01 16:10     ` Jeff King [this message]
2020-07-01 16:14       ` Fabio Frumento

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=20200701161018.GD6726@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=frumento.fabio@gmail.com \
    --cc=git@vger.kernel.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