From: Jakub Narebski <jnareb@gmail.com>
To: Dario Rodriguez <soft.d4rio@gmail.com>
Cc: Tor Arntsen <tor@spacetec.no>, git@vger.kernel.org
Subject: Re: Installing on AIX fails
Date: Mon, 7 Jun 2010 00:26:19 +0200 [thread overview]
Message-ID: <201006070026.20363.jnareb@gmail.com> (raw)
In-Reply-To: <AANLkTikbAShMuOvFra8bLT2PmU7s_iUQhr4RY7oD3LLa@mail.gmail.com>
On Sat, 5 Jun 2010, Dario Rodriguez wrote:
> On Sat, Jun 5, 2010 at 8:44 AM, Jakub Narebski <jnareb@gmail.com> wrote:
>> Tor Arntsen <tor@spacetec.no> writes:
>>>
>>> Maybe you could get away with just using the script-version of install
>>> which comes with coreutils itself (because it'll need an install tool
>>> to use before 'install' itself is installed..).
>>>
>>> I'm attaching a copy. To use it it should be sufficient to use
>>> INSTALL=path-to/install-sh make install
>>> or something like that.
>>
>> I wonder if it would be better to simply include fallback portable
>> install-sh in git sources.
>>
>> BTW. shouldn't we define and use INSTALL_D in Makefile?
>
> I think so about the install-sh, but about the Makefiles I wonder if
> it's not better to reuse current INSTALL, maybe if install-sh is used,
> then there is no need for using other 'install' program, excepting the
> case in wich the user sets INSTALL commandline.
Well, if there were install-sh script in git sources, we could uncomment
#AC_PROG_INSTALL # needs install-sh or install.sh in sources
line in configure.ac, then ./configure would automatically detect and
select 'install' program or script to use. The autoconf documentation
(autoconf.info) says:
This macro screens out various instances of `install' known not to
work. It prefers to find a C program rather than a shell script,
for speed. [...]
Autoconf comes with a copy of `install-sh' that you can use. If
you use `AC_PROG_INSTALL', you must include either `install-sh' or
`install.sh' in your distribution, or `configure' will produce an
error message saying it can't find them--even if the system you're
on has a good `install' program. This check is a safety measure
to prevent you from accidentally leaving that file out, which
would prevent your package from installing on systems that don't
have a BSD-compatible `install' program.
So I guess we should also prefer install program for speed, even if we
do not use ./configure script.
--
Jakub Narębski
Poland
next prev parent reply other threads:[~2010-06-06 22:26 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
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 [this message]
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=201006070026.20363.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=soft.d4rio@gmail.com \
--cc=tor@spacetec.no \
/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).