From: Akira Kitada <akitada@gmail.com>
To: git@vger.kernel.org
Subject: Git 1.7.3.1 cannot be built on FreeBSD 4 with gcc 2.95
Date: Sun, 10 Oct 2010 11:52:45 +0900 [thread overview]
Message-ID: <AANLkTi=z1vqpimP_5kS_AxcVypM5Dx75p--XG8E3uSx=@mail.gmail.com> (raw)
Hello,
I'm hitting the following errors during Git 1.7.3.1 build on FreeBSD 4.
I didn't see this problem when I built 1.7.0.1 so I should be
introduced in the recent versions.
Is there any reports regarding this?
Thank you
$ ./configure && gmake -j 1 V=1
...
rm -f git-add--interactive git-add--interactive+ && \
INSTLIBDIR=`MAKEFLAGS= gmake -C perl -s --no-print-directory instlibdir` && \
sed -e '1{' \
-e ' s|#!.*perl|#!/usr/bin/perl|' \
-e ' h' \
-e ' s=.*=use lib (split(/:/, $ENV{GITPERLLIB} || "'"$INSTLIBDIR"'"));=' \
-e ' H' \
-e ' x' \
-e '}' \
-e 's/@@GIT_VERSION@@/1.7.3.1/g' \
git-add--interactive.perl >git-add--interactive+ && \
chmod +x git-add--interactive+ && \
mv git-add--interactive+ git-add--interactive
'INSTALLSITEMAN3DIR' is not a known MakeMaker parameter name.
'INSTALL_BASE' is not a known MakeMaker parameter name.
Writing perl.mak for Git
'INSTALLSITEMAN3DIR' is not a known MakeMaker parameter name.
'INSTALL_BASE' is not a known MakeMaker parameter name.
Writing perl.mak for Git
gmake[2]: *** [perl.mak] Error 1
gmake[1]: *** [instlibdir] Error 2
gmake: *** [git-add--interactive] Error 2
next reply other threads:[~2010-10-10 2:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 2:52 Akira Kitada [this message]
2010-10-10 4:46 ` Git 1.7.3.1 cannot be built on FreeBSD 4 with gcc 2.95 Tay Ray Chuan
2010-10-10 5:25 ` Akira Kitada
2010-10-10 5:48 ` Tay Ray Chuan
2010-10-10 6:03 ` Akira Kitada
2010-10-10 11:03 ` Ævar Arnfjörð Bjarmason
2010-10-10 11:06 ` Junio C Hamano
2010-10-11 1:31 ` Akira Kitada
2010-10-12 3:59 ` Junio C Hamano
2010-10-12 4:36 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=z1vqpimP_5kS_AxcVypM5Dx75p--XG8E3uSx=@mail.gmail.com' \
--to=akitada@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).