From: Jeff King <peff@peff.net>
To: Stephen Fisher <sfisher@SDF.ORG>
Cc: git@vger.kernel.org
Subject: Re: Git's configure script --mandir doesn't work
Date: Wed, 10 Dec 2014 14:55:09 -0500 [thread overview]
Message-ID: <20141210195509.GB22969@peff.net> (raw)
In-Reply-To: <20141210194150.GA28190@SDF.ORG>
On Wed, Dec 10, 2014 at 12:41:50PM -0700, Stephen Fisher wrote:
> I'm executing ./configure --mandir=/usr/local/man --disable-pthreads
> then gmake and gmake install. I'm using gmake (GNU make) because I get
> Makefile errors with the regular BSD make, but that's another issue.
You have to build git with GNU make; there are several GNU-isms in the
Makefile.
> I'm disabling pthreads because there is a linking error for undefined
> references to a few functions (I probably need to pass -lpthread in
> LDFLAGS, but haven't tried that yet).
We should link against -lpthread automatically unless pthreads are
disabled. So that may be an issue worth investigating.
> I noticed text files in Documentation/ that look like the content of man
> pages, and when I run gmake in that directory, I get an error about
> asciidoc missing to make an HTML file. Is asciidoc required for the man
> pages as well?
Yes, you need asciidoc to build the manpages. However, there is a "make
quick-install-man" target which will install pre-formatted manpages.
You'll need to:
git clone git://git.kernel.org/pub/scm/git/git-manpages.git
next to your git.git clone. If you are installing from tarballs, I think
there are manpage tarballs on kernel.org, as well.
> I don't see any files that appear to be man page format
> other than in perl/blib/man3 and those are installed (but not under the
> mandir prefix, rather the default /usr/local/share/man prefix).
It sounds like the manpage install bailed due to asciidoc failing. So
the remaining bug is that the perl Makefile does not respect $(mandir).
That does not surprise me too much. We use perl's MakeMaker to build that
Makefile, and it looks like we just pass in the prefix, not individual
paths.
-Peff
prev parent reply other threads:[~2014-12-10 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 23:25 Git's configure script --mandir doesn't work Stephen Fisher
2014-12-05 9:36 ` Jeff King
2014-12-10 19:41 ` Stephen Fisher
2014-12-10 19:55 ` Jeff King [this message]
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=20141210195509.GB22969@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=sfisher@SDF.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 NNTP newsgroup(s).