git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Dario Rodriguez <soft.d4rio@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Installing on AIX fails
Date: Thu, 03 Jun 2010 18:12:13 +0200	[thread overview]
Message-ID: <4C07D45D.50503@drmicha.warpmail.net> (raw)
In-Reply-To: <AANLkTinKjEBkn-9ajO4QXyHqY0EOQBGPRgNREaC_p_vQ@mail.gmail.com>

Dario Rodriguez venit, vidit, dixit 03.06.2010 17:32:
> Hi all,
> 
> I was trying to install git in a development and testing server we
> have. The first problem was that AIX 'make' tool does NOT support
> conditionals in makefiles, and display errors such...
> 
> 
> [...]
> "Makefile", line 1003: make: Dependency line needs colon or double
> colon operator.
> "Makefile", line 1007: make: Dependency line needs colon or double
> colon operator.
> "Makefile", line 1009: make: Dependency line needs colon or double
> colon operator.
> "Makefile", line 1011: make: Dependency line needs colon or double
> colon operator.
> [...]
> 
> 
> ... until I get stucked. Well, I solved this by just using GNU make,
> then I compile:
> 
> 
> $ /usr/linux/bin/make prefix=$HOME/apps/ NO_OPENSSL=1 NO_TCLTK=1
> NO_EXPAT=1 PYTHON_PATH=/usr/local/bin/python
> 
> 
> and it all works, with angels singing and everything... a testing repo
> works fine for a test drive without installing, excepting 'git log'
> that just don't display anything.
> Now, when I feel good to install it...
> 
> 
> $ /usr/linux/bin/make prefix=$HOME/apps/ NO_OPENSSL=1 NO_TCLTK=1
> NO_EXPAT=1 PYTHON_PATH=/usr/local/bin/python install
> 
> [...]
> install -d -m 755 '/myhomedir/apps/bin'
> getopt: illegal option -- d
> Usage: install [-c dira] [-f dirb] [-i] [-m] [-M mode] [-O owner]
>                [-G group] [-S] [-n dirc] [-o] [-s] file [dirx ...]
> make: *** [install] Error 2
> 
> 
> 
> Now the installing process fails because of the AIX 'install' tool and
> I wonder, can I patch/configure the installing process for AIX? May be
> a set of utils for building in such systems would help some people.

AIX tools are a pain in the back end. If you want to compile & install
anything GNU there you need better tools. In case of install, there's
often something in /usr/ucb or /usr/ccs.

Are you using gcc or xlc btw?

> 
> PD: If you don't understand me please let me know it and I will try
> again : )  My english could be horrible since I'm Argentinian.

It's certainly good enough!

> PD2: I don't know if AIX python path is always /usr/local/bin/python,
> but I've seen that git Makefiles set /usr/local/bin/python for FreeBSD
> only:
> 
> git_remote_helpers/Makefile:
> ifndef PYTHON_PATH
>         ifeq ($(uname_S),FreeBSD)
>                 PYTHON_PATH = /usr/local/bin/python
>         else
>                 PYTHON_PATH = /usr/bin/python
>         endif
> endif
> 
> I think 'test' the file is a good way for auto-configuration.

You don't need to worry about python for git right now. It's set up for
a few things which are yet to come.

Cheers,
Michael

  parent reply	other threads:[~2010-06-03 16:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 15:32 Installing on AIX fails Dario Rodriguez
2010-06-03 15:41 ` Ævar Arnfjörð Bjarmason
     [not found]   ` <AANLkTikfQdwDoZylaKC_siuwaLrLP4JkMh2fnvwNbxqe@mail.gmail.com>
2010-06-03 20:21     ` Ævar Arnfjörð Bjarmason
2010-06-03 21:22       ` Dario Rodriguez
2010-06-04 14:28         ` Ævar Arnfjörð Bjarmason
2010-06-04 15:07           ` Dario Rodriguez
2010-06-03 16:12 ` Michael J Gruber [this message]
2010-06-04  9:13 ` Tor Arntsen
2010-06-04  9:17   ` Tor Arntsen
2010-06-04 14:22   ` Dario Rodriguez
2010-06-04 14:38     ` Tor Arntsen
2010-06-04 17:21       ` Dario Rodriguez
2010-06-04 17:44         ` Ævar Arnfjörð Bjarmason
2010-06-04 21:03           ` Dario Rodriguez
2010-06-05 11:44       ` Jakub Narebski
2010-06-05 21:59         ` Dario Rodriguez
2010-06-06 22:26           ` Jakub Narebski
2010-06-06 22:29             ` Ævar Arnfjörð Bjarmason

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=4C07D45D.50503@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=soft.d4rio@gmail.com \
    /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).