From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Gaston Gonzalez <gascoar@gmail.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>, git@vger.kernel.org
Subject: Re: Error compiling Git in current master branch
Date: Thu, 8 Mar 2018 17:17:42 +0100 [thread overview]
Message-ID: <20180308161742.26596-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <ce6250a8-c1e2-433d-7d5f-399115aa9f55@gmail.com>
> Just to let you know, I get the following error compiling Git in master
> branch:
>
> $ make prefix=/usr NO_GETTEXT=YesPlease all doc info
> ...
> GEN git-remote-testgit
> GEN perl/build/man/man3/Git.3pm
> Can't write-open perl/build/man/man3/Git.3pm: Permission denied at
> /usr/bin/pod2man line 70.
> Makefile:2317: fallo en las instrucciones para el objetivo
> 'perl/build/man/man3/Git.3pm'
> make: *** [perl/build/man/man3/Git.3pm] Error 13
>
> This didn't happen in v2.16.2. Doing a git-bisect I've got the following
> culprit:
>
> $ git bisect start HEAD v2.16.2 --
> 2530afd3519a34b66e72cc29e7751d650cedc6dd is the first bad commit
That's not the culprit, that's the fix :)
> make clean fails too:
>
> rm -f -r perl/build/
> rm: no se puede borrar 'perl/build/man/man3/Git.3pm': Permiso denegado
> Makefile:2734: fallo en las instrucciones para el objetivo 'clean'
> make: *** [clean] Error 1
Have a look at the permissions of 'perl/build' and its contents, they
are likely owned by root for reasons described in 2530afd's log
message.
next prev parent reply other threads:[~2018-03-08 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 15:53 Error compiling Git in current master branch Gaston Gonzalez
2018-03-08 16:17 ` SZEDER Gábor [this message]
2018-03-08 16:26 ` Gaston Gonzalez
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=20180308161742.26596-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=gascoar@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;
as well as URLs for NNTP newsgroup(s).