From: Johannes Sixt <j.sixt@viscovery.net>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Andreas Ericsson <ae@op5.se>,
git@vger.kernel.org, Sam Vilain <sam@vilain.net>,
arjen@yaph.org
Subject: Re: Building git-1.5.3.7 on HP-UX 11.00
Date: Tue, 11 Dec 2007 14:53:03 +0100 [thread overview]
Message-ID: <475E963F.3000804@viscovery.net> (raw)
In-Reply-To: <20071211143323.27c860db@pc09.procura.nl>
H.Merijn Brand schrieb:
> I have put the output of
>
> % make -i test | & perl -ne'm/^\*\s+ok\s+\d+:/ or print' > git-make-test.log
>
> on http://www.xs4all.nl/~procura/git-make-test.log
>
> which leaves only the following tests as failures:
>
> t3901-i18n-patch.sh t4201-shortlog.sh t5100-mailinfo.sh
> t5405-send-pack-rewind.sh t5500-fetch-pack.sh t5505-remote.sh
> t5510-fetch.sh t5515-fetch-merge-logic.sh t5516-fetch-push.sh
> t5520-pull.sh t5600-clone-fail-cleanup.sh t5700-clone-reference.sh
> t5701-clone-local.sh t6002-rev-list-bisect.sh t6003-rev-list-topo-order.sh
> t6022-merge-rename.sh t6026-merge-attr.sh t6200-fmt-merge-msg.sh
> t7003-filter-branch.sh t9300-fast-import.sh t9301-fast-export.sh
> t9500-gitweb-standalone-no-errors.sh
>
> How close am I to success?
There are a number of tests that pass only if you have iconv, most notably
t3901 and t5100. pull, clone, merge, filter-branch are shell scripts with
plenty of opportunities to stumble over incompatible/unportable constructs.
-- Hannes
next prev parent reply other threads:[~2007-12-11 13:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 13:09 Building git-1.5.3.7 on HP-UX 11.00 H.Merijn Brand
2007-12-04 13:44 ` Johannes Schindelin
2007-12-04 14:03 ` H.Merijn Brand
2007-12-04 14:40 ` Johannes Schindelin
2007-12-04 15:01 ` H.Merijn Brand
2007-12-04 15:14 ` Andreas Ericsson
2007-12-04 15:22 ` H.Merijn Brand
2007-12-04 15:39 ` Johannes Schindelin
2007-12-04 15:56 ` H.Merijn Brand
2007-12-04 16:28 ` Johannes Schindelin
2007-12-05 10:49 ` H.Merijn Brand
2007-12-04 18:05 ` Junio C Hamano
2007-12-04 22:25 ` H.Merijn Brand
2007-12-04 22:46 ` Johannes Schindelin
2007-12-05 8:08 ` H.Merijn Brand
2007-12-04 22:45 ` [PATCH] Do not rely on the exit status of "unset" for unset variables Johannes Schindelin
2007-12-05 8:01 ` H.Merijn Brand
2007-12-10 14:51 ` Building git-1.5.3.7 on HP-UX 11.00 H.Merijn Brand
2007-12-11 8:26 ` Junio C Hamano
2007-12-11 8:54 ` Shawn O. Pearce
2007-12-11 12:57 ` H.Merijn Brand
2007-12-11 9:20 ` Johannes Sixt
2007-12-11 10:42 ` H.Merijn Brand
2007-12-11 11:01 ` Johannes Sixt
2007-12-11 13:33 ` H.Merijn Brand
2007-12-11 13:53 ` Johannes Sixt [this message]
2007-12-04 15:11 ` H.Merijn Brand
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=475E963F.3000804@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=arjen@yaph.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=h.m.brand@xs4all.nl \
--cc=sam@vilain.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.