From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>
To: "carbonated beverage" <ramune@net-ronin.org>
Cc: git@vger.kernel.org
Subject: Re: Test suite failures due to Error.pm issues.
Date: Wed, 9 Apr 2008 10:34:30 +0200 [thread overview]
Message-ID: <b77c1dce0804090134j514811d7mbffdc73dee5a90b7@mail.gmail.com> (raw)
In-Reply-To: <20080408221853.GA3819@net-ronin.org>
On 09/04/2008, carbonated beverage <ramune@net-ronin.org> wrote:
> Hi all,
>
> I was trying to track down the cause of massive test failures in make
> test, and running the failing entries via -v showed the following popping
> up over and over again:
>
> Can't locate Error.pm in @INC (@INC contains: /home/ramune/src/git/git/t/../perl/blib/lib /home/ramune/src/git/git/t/../perl/blib/arch/auto/Git /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8
> /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl .) at /home/ramune/src/git/git/t/../perl/blib/lib/Git.pm line 93.^
> BEGIN failed--compilation aborted at /home/ramune/src/git/git/t/../perl/blib/lib/Git.pm line 93.^
> Compilation failed in require at /home/ramune/src/git/git/t/../git-add--interactive line 5.^
> BEGIN failed--compilation aborted at /home/ramune/src/git/git/t/../git-add--interactive line 5.^
>
> Since git has private-Error.pm file, shouldn't that be picked up by the
> make test invocation?
The private Error file is not installed if perl/Makefile.PL detects
than an Error.pm recent enough on your system. Do you actually have
perl/blib/lib/Error.pm ? Try to run (cd perl; make clean; cd ..; make)
and try the tests again.
next prev parent reply other threads:[~2008-04-09 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 22:18 Test suite failures due to Error.pm issues carbonated beverage
2008-04-09 8:34 ` Rafael Garcia-Suarez [this message]
2008-04-13 3:04 ` carbonated beverage
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=b77c1dce0804090134j514811d7mbffdc73dee5a90b7@mail.gmail.com \
--to=rgarciasuarez@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramune@net-ronin.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).