From: Mike Ralphson <mike.ralphson@gmail.com>
To: Perry Smith <pedzsan@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: git 1.6.1 on AIX 5.3
Date: Wed, 28 Jan 2009 09:48:25 +0000 [thread overview]
Message-ID: <e2b179460901280148u6413c650l25f09b60d753a8e6@mail.gmail.com> (raw)
In-Reply-To: <BAD975AD-323D-4278-8405-0B57E7202797@gmail.com>
2009/1/28 Perry Smith <pedzsan@gmail.com>:
> Sorry... I thought "out of tree" was a universal term.
No, my mistake, I didn't think about what you meant.
> About 90% of the open source configure / autoconf code out there can do this
> with. The other 10% you can not. I like it because when things die, its easier to
> grep around the source tree and I blow away the build directory and start back over and
> I know that I'm starting fresh.
Even if you're only building git, unless disc space is tight, I'd
probably recommend cloning the git.git repository, then you can either
use make clean or git clean, plus it makes updating to
latest/arbitrary versions easier. Anyway, I don't think your setup is
wrong.
> Yea, part of my larger quest is to start a web site to provide AIX builds
> of open source images as installp images. I have not added iconv to the
> mix yet because I fear bad interactions with GNU's and AIX's. In theory,
> AIX's commands should use AIX's library but it would not surprise me if there are
> a few AIX applications that are not built properly.
A pity package distribution for AIX is so fragmented, but when IBM had
the ball, they dropped it. Mail me if you want links to other existing
sites who might appreciate contributed builds.
> I assume the GIT_SKIP_TESTS is done:
It's documented in test/README
> I just tried setting SHELL_PATH (and exporting it) and the make test gets
> into the second batch and then fails two tests. ... now test 10 of t0001.sh
> fails because test_cmp can not be found.
>
> Is that a GNU tool? (I didn't see it in git or coreutils.)
As Peff said, there's a wrapper around either diff -u or a user
supplied comparison tool (e.g. cmp) set in GIT_TEST_CMP. Setting it to
cmp works fine on AIX if you don't have a diff which takes -u on your
PATH.
As (at the moment) you need bash, gcc, gmake and ginstall to build,
test and (maybe) run all parts of git on AIX, I haven't set up a clean
environment to try and flush out any other quirks to get git to
build/test/run on a stock AIX with no GNU tools installed. For obvious
reasons such AIX machines being used for dev purposes are (I believe)
rare.
Mike
prev parent reply other threads:[~2009-01-28 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 20:02 git 1.6.1 on AIX 5.3 Perry Smith
2009-01-26 21:00 ` Jeff King
2009-01-26 22:32 ` Mike Ralphson
2009-01-26 22:57 ` Perry Smith
2009-01-27 3:52 ` Jeff King
2009-01-27 10:10 ` Mike Ralphson
2009-01-28 1:35 ` Perry Smith
2009-01-28 7:01 ` Jeff King
2009-01-28 7:37 ` Junio C Hamano
2009-01-28 7:42 ` Jeff King
2009-01-28 15:03 ` Perry Smith
2009-01-28 9:48 ` Mike Ralphson [this message]
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=e2b179460901280148u6413c650l25f09b60d753a8e6@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=git@vger.kernel.org \
--cc=pedzsan@gmail.com \
--cc=peff@peff.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 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).