From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: [BUG?] t9500 --debug prints "sh: ++GIT_BINDIR++/git: not found"
Date: Wed, 27 Oct 2010 15:49:54 -0500 [thread overview]
Message-ID: <20101027204954.GA31386@burratino> (raw)
Hi,
Trying to run t9500-gitweb-standalone-no-errors.sh, I find:
$ sh t9500-gitweb-standalone-no-errors.sh --debug
ok 1 - no commits: projects_list (implicit)
sh: ++GIT_BINDIR++/git: not found
ok 2 - no commits: projects_index
sh: ++GIT_BINDIR++/git: not found
ok 3 - no commits: .git summary (implicit)
[...]
config.mak reads:
CFLAGS = -g -O2 -Wall -Wdeclaration-after-statement
NO_OPENSSL=1
NO_EXPAT=1
COMPUTE_HEADER_DEPENDENCIES=1
USE_NSEC=1
ASCIIDOC8=1
ASCIIDOC_NO_ROFF=1
and there is no config.mak.autogen or other source of build flags.
Ideas? Is this expected behavior?
next reply other threads:[~2010-10-27 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 20:49 Jonathan Nieder [this message]
2010-10-27 21:21 ` [BUG?] t9500 --debug prints "sh: ++GIT_BINDIR++/git: not found" Jakub Narebski
2010-10-27 21:34 ` Jonathan Nieder
2010-10-27 22:32 ` Jakub Narebski
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=20101027204954.GA31386@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).