git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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: Tue, 27 Jan 2009 10:10:39 +0000	[thread overview]
Message-ID: <e2b179460901270210q69fe1e42xb801553e4e9005e9@mail.gmail.com> (raw)
In-Reply-To: <9E98493A-B17A-4905-8BEA-3E0B837961D6@gmail.com>

2009/1/26 Perry Smith <pedzsan@gmail.com>:
> Thanks guys.  I picked up coreutils version 7.   I didn't
> install them but just moved ginstall over to /usr/local/bin.
>
> A few other comments:  I had to add in the --without-tcltk flag.  I don't
> have tcl installed but the config did not autodetect that it was not present.

Yup, I usually build with NO_TCLTK=YesPlease in my config.mak, which
you can see from the link Peff posted.

When you said 'out of tree builds' I thought you meant using the AIX
defaults in the Makefile without running ./configure, but it seems
not, you meant is a clone of the tree buildable by itself or are only
release snapshots buildable. Sorry.

./configure is (deliberately) a second-class citizen in the world of
git, and may still get you a slightly suboptimal build compared with
the defaults on platforms such as AIX... e.g. it doesn't test for
performance-related switches such as INTERNAL_QSORT. If you have run
configure, there's some file you need to blow away to get back to a
non-autoconf world... is it config.mak.autogen?

Despite that, your problem with --without-tcltk falling back to wish,
but not falling back if that isn't installed does look like something
we should fix, as per Peff's mail.

> I can't tell if make test is happy or not.  The output looks like its happy
> but the exit code is 2.
>
> Below is my "configure" script if anyone is interested.
>
> #!/usr/bin/env bash
>
> export CONFIG_SHELL=/usr/local/bin/bash
> export LDFLAGS='-L/usr/local/lib -L/usr/local/ssl/lib'
> export CFLAGS='-I/usr/local/include -I/usr/local/ssl/include'
> export CC=gcc
> echo CONFIG_SHELL set to ${CONFIG_SHELL}
>
> ${CONFIG_SHELL} ../../src/git-1.6.1/configure --without-tcltk
>
> #
> # Note that to install you need to do:
> # make INSTALL=ginstall install
> # to use GNU's install program

I build with SHELL_PATH={path}/bash as well. If I don't, the test
suite exits after t0000-basic.sh with an unexpected error despite
passing all the tests.

gmake -C t/ all
gmake[1]: Entering directory `/usr/local/src/gitbuild/t'
rm -f -r test-results
gmake aggregate-results-and-cleanup
gmake[2]: Entering directory `/usr/local/src/gitbuild/t'
*** t0000-basic.sh ***
* passed all remaining 40 test(s)
FATAL: Unexpected exit with code 0
gmake[2]: *** [t0000-basic.sh] Error 1
gmake[2]: Leaving directory `/usr/local/src/gitbuild/t'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/usr/local/src/gitbuild/t'
gmake: *** [test] Error 2

Is that what you're seeing? There's many more test scripts than that 8-)

With GIT_SKIP_TESTS='t3900 t3901 t5100.[12] t8005' (to omit some cases
not handled by the version of iconv I have access to on all the AIX
boxes I deploy to) the test suit runs to completion on AIX 5.3 for me.

BTW Are you running AIX's make or GNU make?

Mike

  parent reply	other threads:[~2009-01-27 10:12 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 [this message]
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

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=e2b179460901270210q69fe1e42xb801553e4e9005e9@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.
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).