All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: Andy Dougherty <doughera@lafayette.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Explain what 'ginstall' is
Date: Tue, 18 Dec 2007 13:32:59 +0100	[thread overview]
Message-ID: <200712181333.01051.jnareb@gmail.com> (raw)
In-Reply-To: <20071218121115.1c893dc4@pc09.procura.nl>

H.Merijn Brand wrote:
> On Tue, 18 Dec 2007 10:14:38 +0100, Jakub Narebski <jnareb@gmail.com> wrote:
>> On Tue, 18 Dec 2007, H.Merijn Brand wrote:
>>> On Tue, 18 Dec 2007 09:20:38 +0100, Jakub Narebski <jnareb@gmail.com> wrote:
>>>> On Tue, 18 Dec 2007, H.Merijn Brand wrote:
>>>>> On Mon, 17 Dec 2007 17:21:08 -0800 (PST), Jakub Narebski wrote:
>>>>>>
>>>>>> Second, the default autoconf macro AC_PROG_INSTALL *requires* that
>>>>>> there is BSD-compatible `install' program (as 'install-sh' or
>>>>>> 'install.sh') in the sources.  Adding such script is (I think) not a
>>>>>> problem; finding minimal portable[*1*] script is.  
>>>>>> So if you know one... 
>>>> 
>>>> [...]. There is need for BSD-compatibile
>>>> `install` program as 'install-sh', not 'make-install' script. The idea
>>>> is to use system-provided 'install' if it exists and is compatibile,
>>> 
>>> There lies the problem. HP-UX does have an 'install', but it is not
>>> compatible, and chances are (very) small that people have installed
>>> the GNU or any other BSD compliant install.
>>> 
>>>> because it should be faster than script version, and fallback to 
>>>> provided install-sh only if system install is not found.
>>> 
>>> The problem again. It *does* find install, but it turns out to be
>>> unusable.
>> 
>> Could you check if ./configure correctly uses install-sh in your case?
>> Copy install-sh from for example autotools[*1*] (e.g. libtool has one)
>> to the git sources, uncomment line with AC_PROG_INSTALL in configure.ac,
>> generate configure script using "make configure" and check what
>> ./configure chooses.
>> 
>> In my case it is:
>> 
>>   $ cp /usr/share/libtool/install-sh .
>>   $ make configure
>>   GIT_VERSION = 1.5.4.rc0.56.g6fbe-dirty
>>       GEN configure
>>   $ ./configure
>>   configure: CHECKS for programs
>>   [...]
>>   checking for a BSD-compatible install... /usr/bin/install -c
>> 
>> What is ./configure output in your case?

 
> /pro/3gl/LINUX/git-2007-12-17 119> cp /pro/3gl/GNU/gcc/r3/gcc-4.2.2/install-sh install-sh

> -- uncommented the AC_PROG_INSTALL line ...

> OK, rebuild configure ...
> 
> a5:/pro/3gl/LINUX/git-2007-12-17 129> make configure
>     GEN configure
> a5:/pro/3gl/LINUX/git-2007-12-17 130> rm config.{log,status}
> a5:/pro/3gl/LINUX/git-2007-12-17 131> configure --prefix=/pro/local --disable-nls --without-iconv --with-perl=/pro/bin/perl> & config-log
> a5:/pro/3gl/LINUX/git-2007-12-17 132> grep -w install config-log config.log config.status
> config-log:checking for a BSD-compatible install... /opt/imake/bin/install -c
> config.log:configure:2218: checking for a BSD-compatible install
> config.log:configure:2273: result: /opt/imake/bin/install -c
> config.log:ac_cv_path_install='/opt/imake/bin/install -c'
> config.status:INSTALL="/opt/imake/bin/install -c"

Does chosen by ./configure script 'install' binary, namely 
/opt/imake/bin/install works correctly, meaning does it install
git correctly?

-- 
Jakub Narebski
Poland

  reply	other threads:[~2007-12-18 12:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17 21:46 [PATCH] Explain what 'ginstall' is Andy Dougherty
2007-12-18  1:21 ` Jakub Narebski
2007-12-18  7:38   ` H.Merijn Brand
2007-12-18  8:20     ` Jakub Narebski
2007-12-18  8:38       ` H.Merijn Brand
2007-12-18  9:14         ` Jakub Narebski
2007-12-18 11:11           ` H.Merijn Brand
2007-12-18 12:32             ` Jakub Narebski [this message]
2007-12-18 13:32               ` H.Merijn Brand
2007-12-18 14:03                 ` Jakub Narebski
2007-12-18 14:27                   ` H.Merijn Brand
2007-12-23  9:01   ` Jan Hudec

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=200712181333.01051.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=doughera@lafayette.edu \
    --cc=git@vger.kernel.org \
    --cc=h.m.brand@xs4all.nl \
    /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.