From: Junio C Hamano <gitster@pobox.com>
To: NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com>
Cc: Derrick Stolee <derrickstolee@github.com>,
Luna Jernberg <droidbittin@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
git@vger.kernel.org, Hariom verma <hariom18599@gmail.com>
Subject: Re: [Outreachy] internship contribution
Date: Tue, 11 Oct 2022 21:42:52 -0700 [thread overview]
Message-ID: <xmqqleplmz3n.fsf@gitster.g> (raw)
In-Reply-To: <CA+PPyiEms=f7=rXkvfmaazNkxKS1-VA-XJZOrhieQEut8f7QWA@mail.gmail.com> (NSENGIYUMVA WILBERFORCE's message of "Wed, 12 Oct 2022 06:31:52 +0300")
NSENGIYUMVA WILBERFORCE <nsengiyumvawilberforce@gmail.com> writes:
> Hi team, I am reading through "My first contribution"
> when I run make all doc, I get the following;
>
> SUBDIR git-gui
> SUBDIR gitk-git
> SUBDIR templates
> make -C Documentation all
> make[1]: Entering directory '/mnt/c/Users/USER/documents/git/Documentation'
> make[2]: Entering directory '/mnt/c/Users/USER/documents/git'
> make[2]: 'GIT-VERSION-FILE' is up to date.
> make[2]: Leaving directory '/mnt/c/Users/USER/documents/git'
> XMLTO git-version.1
> /bin/sh: 1: xmlto: not found
> make[1]: *** [Makefile:355: git-version.1] Error 127
> make[1]: Leaving directory '/mnt/c/Users/USER/documents/git/Documentation'
> make: *** [Makefile:2720: doc] Error 2
>
> How should I go about it?
Googling "xmlto: not found", the first result is
https://command-not-found.com/xmlto
The page lists how to get and install it for various platforms, and
WSL/Windows should be included there.
I believe "My first contribution" recommends to first read the
top-level INSTALL before continuing (and if not, it should be
updated to). Simpler things first---building and installing the
vanilla source code without any of your changes should be simpler
and you should become confident in doing that, before you start
modifying anything. Otherwise, when you encounter a problem, you
would not be able to tell if you broke it with your change, or your
basic set-up is not complete (e.g. missing necessary tools like
xmlto) and unable to build and install from even vanilla set of
sources.
Have fun.
next prev parent reply other threads:[~2022-10-12 4:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 4:37 [Outreachy] internship contribution NSENGIYUMVA WILBERFORCE
2022-10-10 8:19 ` Christian Couder
2022-10-10 12:18 ` NSENGIYUMVA WILBERFORCE
2022-10-10 16:22 ` Christian Couder
2022-10-10 16:33 ` Derrick Stolee
2022-10-10 16:57 ` Luna Jernberg
2022-10-10 18:17 ` NSENGIYUMVA WILBERFORCE
2022-10-10 18:22 ` Derrick Stolee
2022-10-11 6:48 ` NSENGIYUMVA WILBERFORCE
2022-10-12 3:31 ` NSENGIYUMVA WILBERFORCE
2022-10-12 4:42 ` Junio C Hamano [this message]
2022-10-12 6:45 ` Đoàn Trần Công Danh
2022-10-12 10:37 ` NSENGIYUMVA WILBERFORCE
2022-10-12 14:21 ` Christian Couder
2022-10-12 15:18 ` Đoàn Trần Công Danh
2022-10-12 16:37 ` NSENGIYUMVA WILBERFORCE
[not found] ` <CA+fEeODMVNrnFRbuNVgbBShSA2Juo8Ux5ahd2J8nCfmPetdpvA@mail.gmail.com>
2022-10-13 10:52 ` Christian Couder
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=xmqqleplmz3n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=derrickstolee@github.com \
--cc=droidbittin@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=nsengiyumvawilberforce@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).