* [PATCH] Explain what 'ginstall' is
@ 2007-12-17 21:46 Andy Dougherty
2007-12-18 1:21 ` Jakub Narebski
0 siblings, 1 reply; 12+ messages in thread
From: Andy Dougherty @ 2007-12-17 21:46 UTC (permalink / raw)
To: git
While trying git out on Solaris 8, the 'make install' step failed because
I don't have a 'ginstall' command. After puzzling over it for a while,
I finally figured out that
a) it's referring to the 'install' command that is now part of the
GNU coreutils package, and
b) it's probably unnecessary, as using the Solaris install command
gave me the same results. (However, I didn't do anything fancy,
so it may be that in some scenarios using 'ginstall' matters.
I didn't do anything other than a very simple test.)
Anyway, this patch documents it a tiny bit more. Perhaps configure
should just go looking for a suitable install program instead of
assuming everyone has one.
--- git-1.5.4.rc0/Makefile 2007-12-12 21:29:16.000000000 -0500
+++ git-andy/Makefile 2007-12-17 15:15:12.000000000 -0500
@@ -416,6 +416,9 @@
NO_STRLCPY = YesPlease
NO_MEMMEM = YesPlease
endif
+# For SunOS, this assumes you have ginstall from the
+# GNU coreutils package. It's not clear whether that
+# is actually necessary.
ifeq ($(uname_S),SunOS)
NEEDS_SOCKET = YesPlease
NEEDS_NSL = YesPlease
--
Andy Dougherty doughera@lafayette.edu
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH] Explain what 'ginstall' is 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-23 9:01 ` Jan Hudec 0 siblings, 2 replies; 12+ messages in thread From: Jakub Narebski @ 2007-12-18 1:21 UTC (permalink / raw) To: Andy Dougherty; +Cc: git Andy Dougherty <doughera@lafayette.edu> writes: > [...]. Perhaps configure > should just go looking for a suitable install program instead of > assuming everyone has one. First, configure is, and (I think) consensus is that it should remain optional. This means that Makefile "guess" section should have good defaults for your operating system. 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... Footnotes: ---------- [*1*] By "portable" I mean here 'git portable', i.e. requiring only those shell constructs/features that git require, not necessary insanelt portable the way ./configure script is. -- Jakub Narebski Poland ShadeHawk on #git ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 1:21 ` Jakub Narebski @ 2007-12-18 7:38 ` H.Merijn Brand 2007-12-18 8:20 ` Jakub Narebski 2007-12-23 9:01 ` Jan Hudec 1 sibling, 1 reply; 12+ messages in thread From: H.Merijn Brand @ 2007-12-18 7:38 UTC (permalink / raw) To: Jakub Narebski; +Cc: Andy Dougherty, git On Mon, 17 Dec 2007 17:21:08 -0800 (PST), Jakub Narebski <jnareb@gmail.com> wrote: > Andy Dougherty <doughera@lafayette.edu> writes: > > > [...]. Perhaps configure > > should just go looking for a suitable install program instead of > > assuming everyone has one. > > First, configure is, and (I think) consensus is that it should remain > optional. This means that Makefile "guess" section should have good > defaults for your operating system. And what if you OS *does* have an install, but one that is completely useless^Wdifferent from the GNU install? Like the utterly useless install on HP-UX. > 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; Yeah! > finding minimal portable[*1*] script is. So if you know one... > > Footnotes: > ---------- > [*1*] By "portable" I mean here 'git portable', i.e. requiring only > those shell constructs/features that git require, not necessary > insanelt portable the way ./configure script is. Something like this? (gui part still missing). This is what I now use --8<--- make-install #!/bin/sh PREFIX=/pro/local BINDIR=$PREFIX/bin SHARED=$PREFIX/share for p in git-fetch-pack git-hash-object git-index-pack git-fast-import \ git-daemon git-merge-index git-mktag git-mktree git-patch-id \ git-receive-pack git-send-pack git-shell git-show-index \ git-unpack-file git-update-server-info git-upload-pack \ git-pack-redundant git-var git-merge-tree git-imap-send \ git-merge-recursive git-bisect git-checkout git-clone \ git-merge-one-file git-mergetool git-parse-remote git-pull \ git-rebase git-rebase--interactive git-repack git-request-pull \ git-sh-setup git-am git-merge git-merge-stupid git-merge-octopus \ git-merge-resolve git-lost-found git-quiltimport git-submodule \ git-filter-branch git-stash git-add--interactive git-archimport \ git-cvsimport git-relink git-cvsserver git-remote git-cvsexportcommit \ git-send-email git-svn git-instaweb git-merge-subtree ; do rm -f $BINDIR/$p cp $p $BINDIR chmod 755 $BINDIR/$p done cp git $BINDIR cd templates rm -rf $SHARED/git-core mkdir $SHARED/git-core mkdir $SHARED/git-core/templates (cd blt && tar cf - .) | (cd $SHARED/git-core/templates/ && tar xf -) cd .. cd perl make make install UNINST=1 cd .. for p in git-format-patch git-show git-whatchanged git-cherry \ git-get-tar-commit-id git-init git-repo-config git-fsck-objects \ git-cherry-pick git-peek-remote git-status git-add git-annotate \ git-apply git-archive git-blame git-branch git-bundle git-cat-file \ git-check-attr git-checkout-index git-check-ref-format git-clean \ git-commit git-commit-tree git-count-objects git-describe git-diff \ git-diff-files git-diff-index git-diff-tree git-fast-export \ git-fetch git-fetch-pack git-fetch--tool git-fmt-merge-msg \ git-for-each-ref git-fsck git-gc git-grep git-init-db git-log \ git-ls-files git-ls-tree git-ls-remote git-mailinfo git-mailsplit \ git-merge-base git-merge-file git-merge-ours git-mv git-name-rev \ git-pack-objects git-prune git-prune-packed git-push git-read-tree \ git-reflog git-send-pack git-config git-rerere git-reset \ git-rev-list git-rev-parse git-revert git-rm git-shortlog \ git-show-branch git-stripspace git-symbolic-ref git-tag git-tar-tree \ git-unpack-objects git-update-index git-update-ref \ git-upload-archive git-verify-pack git-verify-tag git-write-tree \ git-show-ref git-pack-refs ; do rm -f $BINDIR/$p ln $BINDIR/git $BINDIR/$p done -->8--- -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 7:38 ` H.Merijn Brand @ 2007-12-18 8:20 ` Jakub Narebski 2007-12-18 8:38 ` H.Merijn Brand 0 siblings, 1 reply; 12+ messages in thread From: Jakub Narebski @ 2007-12-18 8:20 UTC (permalink / raw) To: H.Merijn Brand; +Cc: Andy Dougherty, git On Tue, 18 Dec 2007, H.Merijn Brand wrote: > On Mon, 17 Dec 2007 17:21:08 -0800 (PST), Jakub Narebski wrote: > >> Andy Dougherty <doughera@lafayette.edu> writes: >> >>> [...]. Perhaps configure >>> should just go looking for a suitable install program instead of >>> assuming everyone has one. >> >> First, configure is, and (I think) consensus is that it should remain >> optional. This means that Makefile "guess" section should have good >> defaults for your operating system. > > And what if you OS *does* have an install, but one that is completely > useless^Wdifferent from the GNU install? Like the utterly useless > install on HP-UX. Then "guess" section should have INSTALL=ginstall, or something. Or just install with INSTALL=/opt/bin/ginstall make install or something like that. >> 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; > > Yeah! > >> finding minimal portable[*1*] script is. So if you know one... >> >> Footnotes: >> ---------- >> [*1*] By "portable" I mean here 'git portable', i.e. requiring only >> those shell constructs/features that git require, not necessary >> insanelt portable the way ./configure script is. > > Something like this? (gui part still missing). This is what I now > use > > --8<--- make-install Errr... please read more carefully. 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, because it should be faster than script version, and fallback to provided install-sh only if system install is not found. install-sh has to understand '-d' and '-m <mode>' switches for git install purposes, and probably implement all three (src dest, src dir, dir) formats. -- Jakub Narebski Poland ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 8:20 ` Jakub Narebski @ 2007-12-18 8:38 ` H.Merijn Brand 2007-12-18 9:14 ` Jakub Narebski 0 siblings, 1 reply; 12+ messages in thread From: H.Merijn Brand @ 2007-12-18 8:38 UTC (permalink / raw) To: Jakub Narebski; +Cc: Andy Dougherty, git 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: > > > >> Andy Dougherty <doughera@lafayette.edu> writes: > >> > >>> [...]. Perhaps configure > >>> should just go looking for a suitable install program instead of > >>> assuming everyone has one. > >> > >> First, configure is, and (I think) consensus is that it should remain > >> optional. This means that Makefile "guess" section should have good > >> defaults for your operating system. > > > > And what if you OS *does* have an install, but one that is completely > > useless^Wdifferent from the GNU install? Like the utterly useless > > install on HP-UX. > > Then "guess" section should have INSTALL=ginstall, or something. > Or just install with > > INSTALL=/opt/bin/ginstall make install Chances are close to zero that HP-UX systems have installed any working or compliant version of install > or something like that. > > >> 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; > > > > Yeah! > > > >> finding minimal portable[*1*] script is. So if you know one... > >> > >> Footnotes: > >> ---------- > >> [*1*] By "portable" I mean here 'git portable', i.e. requiring only > >> those shell constructs/features that git require, not necessary > >> insanelt portable the way ./configure script is. > > > > Something like this? (gui part still missing). This is what I now > > use > > > > --8<--- make-install > > Errr... please read more carefully. 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. > install-sh has to understand '-d' and '-m <mode>' switches for git > install purposes, and probably implement all three (src dest, src dir, > dir) formats. BTW the same, but worse exists for the 'patch' program. On HP-UX there is a program called 'patch' which is used for system upgrades, but it has nothing to do with the patch util the rest of the world so happily uses. So far that is used in a few places in the test suite, but I heared it would not be too hard to eliminate the use of the hard-coded patch util -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 8:38 ` H.Merijn Brand @ 2007-12-18 9:14 ` Jakub Narebski 2007-12-18 11:11 ` H.Merijn Brand 0 siblings, 1 reply; 12+ messages in thread From: Jakub Narebski @ 2007-12-18 9:14 UTC (permalink / raw) To: H.Merijn Brand; +Cc: Andy Dougherty, git 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? Footnotes: ---------- [*1*] Or for example http://svn.scheffers.net/zlib/tclconfig/install-sh which is smaller (2189 bytes vs. 9233 autotools one, or 10970 from kapptemplate (kdesdk 3.5.3)). -- Jakub Narebski Poland ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 9:14 ` Jakub Narebski @ 2007-12-18 11:11 ` H.Merijn Brand 2007-12-18 12:32 ` Jakub Narebski 0 siblings, 1 reply; 12+ messages in thread From: H.Merijn Brand @ 2007-12-18 11:11 UTC (permalink / raw) To: Jakub Narebski; +Cc: Andy Dougherty, git 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 112 > rm config.{log,status} /pro/3gl/LINUX/git-2007-12-17 113 > configure --prefix=/pro/local --disable-nls --without-iconv --with-perl=/pro/bin/perl >& config-log /pro/3gl/LINUX/git-2007-12-17 114 > grep -w install !$ grep -w install config-log Exit 1 /pro/3gl/LINUX/git-2007-12-17 115 > The system could have used either one of these: /pro/3gl/LINUX/git-2007-12-17 116 > ll /pro/local/share/automa*/install-sh 258090 -rwxr-xr-x 1 merijn softwr 9212 Sep 2 2004 /pro/local/share/automake-1.9/install-sh 77938 -rwxr-xr-x 1 merijn softwr 5598 Oct 4 2001 /pro/local/share/automake/install-sh /pro/3gl/LINUX/git-2007-12-17 119 > cp /pro/3gl/GNU/gcc/r3/gcc-4.2.2/install-sh install-sh /pro/3gl/LINUX/git-2007-12-17 120 > rm config.{log,status} /pro/3gl/LINUX/git-2007-12-17 121 > configure --prefix=/pro/local --disable-nls --without-iconv --with-perl=/pro/bin/perl > & config-log /pro/3gl/LINUX/git-2007-12-17 122 > grep -w install config-log Exit 1 /pro/3gl/LINUX/git-2007-12-17 123 > ll install-sh 121737 -rwxrwxr-x 1 merijn softwr 9233 Dec 18 12:06 install-sh /pro/3gl/LINUX/git-2007-12-17 124 > -- uncommented the AC_PROG_INSTALL line ... a5:/pro/3gl/LINUX/git-2007-12-17 125 > rm config.{log,status} a5:/pro/3gl/LINUX/git-2007-12-17 126 > configure --prefix=/pro/local --disable-nls --without-iconv --with-perl=/pro/bin/perl > & config-log a5:/pro/3gl/LINUX/git-2007-12-17 127 > grep -w install config-log Exit 1 a5:/pro/3gl/LINUX/git-2007-12-17 128 > grep -w install config.log config.status Exit 1 a5:/pro/3gl/LINUX/git-2007-12-17 129 > 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" a5:/pro/3gl/LINUX/git-2007-12-17 133 > > Footnotes: > ---------- > [*1*] Or for example http://svn.scheffers.net/zlib/tclconfig/install-sh > which is smaller (2189 bytes vs. 9233 autotools one, or 10970 from > kapptemplate (kdesdk 3.5.3)). -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 11:11 ` H.Merijn Brand @ 2007-12-18 12:32 ` Jakub Narebski 2007-12-18 13:32 ` H.Merijn Brand 0 siblings, 1 reply; 12+ messages in thread From: Jakub Narebski @ 2007-12-18 12:32 UTC (permalink / raw) To: H.Merijn Brand; +Cc: Andy Dougherty, git 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 ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 12:32 ` Jakub Narebski @ 2007-12-18 13:32 ` H.Merijn Brand 2007-12-18 14:03 ` Jakub Narebski 0 siblings, 1 reply; 12+ messages in thread From: H.Merijn Brand @ 2007-12-18 13:32 UTC (permalink / raw) To: Jakub Narebski; +Cc: Andy Dougherty, git On Tue, 18 Dec 2007 13:32:59 +0100, Jakub Narebski <jnareb@gmail.com> wrote: > 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? No. I reported this before, but not to the list. This is why I created my own make-install shell: /pro/3gl/LINUX/git-2007-12-17 113 > make install SUBDIR git-gui INDEX lib/ SUBDIR gitk-git make[1]: Nothing to be done for `all'. SUBDIR perl SUBDIR templates install -d -m 755 '/pro/local/bin' rm: /pro/local/bin/ directory Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 mv [-f] [-i] [-e warn|force|ignore] d1 d2 install -d -m 755 '/pro/local/bin' rm: /pro/local/bin/ directory Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 mv [-f] [-i] [-e warn|force|ignore] d1 d2 install git-fetch-pack git-hash-object git-index-pack git-fast-import git-daemon git-merge-index git-mktag git-mktree git-patch-id git-receive-pack git-send-pack git-shell git-show-index git-unpack-file git-update-server-info git-upload-pack git-pack-redundant git-var git-merge-tree git-imap-send git-merge-recursive git-bisect git-checkout git-clone git-merge-one-file git-mergetool git-parse-remote git-pull git-rebase git-rebase--interactive git-repack git-request-pull git-sh-setup git-am git-merge git-merge-stupid git-merge-octopus git-merge-resolve git-lost-found git-quiltimport git-submodule git-filter-branch git-stash git-help--browse git-add--interactive git-archimport git-cvsimport git-relink git-cvsserver git-remote git-cvsexportcommit git-send-email git-svn git-instaweb git-merge- subtree '/pro/local/bin' install git '/pro/local/bin' make -C templates DESTDIR='' install make[1]: Entering directory `/pro/3gl/LINUX/git-2007-12-17/templates' install -d -m 755 '/pro/local/share/git-core/templates/' rm: /pro/local/share/git-core/templates// directory Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 mv [-f] [-i] [-e warn|force|ignore] d1 d2 (cd blt && tar cf - .) | \ (cd '/pro/local/share/git-core/templates/' && tar xf -) make[1]: Leaving directory `/pro/3gl/LINUX/git-2007-12-17/templates' make -C perl prefix='/pro/local' DESTDIR='' install make[1]: Entering directory `/pro/3gl/LINUX/git-2007-12-17/perl' make[2]: Entering directory `/pro/3gl/LINUX/git-2007-12-17/perl' Writing /pro/local/lib/perl5/site_perl/5.8.8/PA-RISC2.0/auto/Git/.packlist Appending installation info to /pro/local/lib/perl5/5.8.8/PA-RISC2.0/perllocal.pod make[2]: Leaving directory `/pro/3gl/LINUX/git-2007-12-17/perl' make[1]: Leaving directory `/pro/3gl/LINUX/git-2007-12-17/perl' make -C gitk-git install make[1]: Entering directory `/pro/3gl/LINUX/git-2007-12-17/gitk-git' install gitk-wish '/pro/local/bin'/gitk make[1]: Leaving directory `/pro/3gl/LINUX/git-2007-12-17/gitk-git' make -C git-gui install make[1]: Entering directory `/pro/3gl/LINUX/git-2007-12-17/git-gui' INDEX lib/ DEST /pro/local/bin rm: /pro/local/bin/ directory Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 mv [-f] [-i] [-e warn|force|ignore] d1 d2 INSTALL 755 git-gui LINK git-citool -> git-gui DEST /pro/local/share/git-gui/lib rm: /pro/local/share/git-gui/lib/ directory Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 mv [-f] [-i] [-e warn|force|ignore] d1 d2 INSTALL 644 tclIndex mv: lib/tclIndex: cannot access: No such file or directory chmod: can't access /pro/local/share/git-gui/lib/tclIndex INSTALL 644 git-gui.ico mv: lib/git-gui.ico: cannot access: No such file or directory chmod: can't access /pro/local/share/git-gui/lib/git-gui.ico DEST /pro/local/share/git-gui/lib/msgs rm: /pro/local/share/git-gui/lib/msgs/ directory Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 mv [-f] [-i] [-e warn|force|ignore] d1 d2 INSTALL 644 de.msg INSTALL 644 hu.msg INSTALL 644 it.msg INSTALL 644 ja.msg INSTALL 644 ru.msg INSTALL 644 zh_cn.msg make[1]: Leaving directory `/pro/3gl/LINUX/git-2007-12-17/git-gui' if test 'z/pro/local/bin' != 'z/pro/local/bin'; \ then \ ln -f '/pro/local/bin/git' \ '/pro/local/bin/git' || \ cp '/pro/local/bin/git' \ '/pro/local/bin/git'; \ fi rm -f '/pro/local/bin/git-format-patch' && ln '/pro/local/bin/git' '/pro/local/bin/git-format-patch' ; rm -f '/pro/local/bin/git-show' && ln '/pro/local/bin/git' '/pro/local/bin/git-show' ; rm -f '/pro/local/bin/git-whatchanged' && ln '/pro/local/bin/git' '/pro/local/bin/git-whatchanged' ; rm -f '/pro/local/bin/git-cherry' && ln '/pro/local/bin/git' '/pro/local/bin/git-cherry' ; rm -f '/pro/local/bin/git-get-tar-commit-id' && ln '/pro/local/bin/git' '/pro/local/bin/git-get-tar-commit-id' ; rm -f '/pro/local/bin/git-init' && ln '/pro/local/bin/git' '/pro/local/bin/git-init' ; rm -f '/pro/local/bin/git-repo-config' && ln '/pro/local/bin/git' '/pro/local/bin/git-repo-config' ; rm -f '/pro/local/bin/git-fsck-objects' && ln '/pro/local/bin/git' '/pro/local/bin/git-fsck-objects' ; rm -f '/pro/local/bin/git-cherry-pick' && ln '/pro/local/bin/git' '/pro/local/bin/git-cherry-pick' ; rm -f '/pro/local/bin/git-peek-remote' && ln '/pro/local/bin/git' '/pro/local/bin/git-peek-re! mote' ; rm -f '/pro/local/bin/git-status' && ln '/pro/local/bin/git' '/pro/local/bin/git-status' ; rm -f '/pro/local/bin/git-add' && ln '/pro/local/bin/git' '/pro/local/bin/git-add' ; rm -f '/pro/local/bin/git-annotate' && ln '/pro/local/bin/git' '/pro/local/bin/git-annotate' ; rm -f '/pro/local/bin/git-apply' && ln '/pro/local/bin/git' '/pro/local/bin/git-apply' ; rm -f '/pro/local/bin/git-archive' && ln '/pro/local/bin/git' '/pro/local/bin/git-archive' ; rm -f '/pro/local/bin/git-blame' && ln '/pro/local/bin/git' '/pro/local/bin/git-blame' ; rm -f '/pro/local/bin/git-branch' && ln '/pro/local/bin/git' '/pro/local/bin/git-branch' ; rm -f '/pro/local/bin/git-bundle' && ln '/pro/local/bin/git' '/pro/local/bin/git-bundle' ; rm -f '/pro/local/bin/git-cat-file' && ln '/pro/local/bin/ git' '/pro/local/bin/git-cat-file' ; rm -f '/pro/local/bin/git-check-attr' && ln '/pro/local/bin/git' '/pro/local/bin/git-check-attr' ; rm -f '/pro/local/bin/git-checkout-index' && ln '/p! ro/local/bin/git' '/pro/local/bin/git-checkout-index' ; rm -f '/pro/l ocal/bin/git-check-ref-format' && ln '/pro/local/bin/git' '/pro/local/bin/git-check-ref-format' ; rm -f '/pro/local/bin/git-clean' && ln '/pro/local/bin/git' '/pro/local/bin/git-clean' ; rm -f '/pro/local/bin/git-commit' && ln '/pro/local/bin/git' '/pro/local/bin/git-commit' ; rm -f '/pro/local/bin/git-commit-tree' && ln '/pro/local/bin/git' '/pro/local/bin/git-commit-tree' ; rm -f '/pro/local/bin/git-count-objects' && ln '/pro/local/bin/git' '/pro/local/bin/git-count-objects' ; rm -f '/pro/local/bin/git-describe' && ln '/pro/local/bin/git' '/pro/local/bin/git-describe' ; rm -f '/pro/local/bin/git-diff' && ln '/pro/local/bin/git' '/pro/local/bin/git-diff' ; rm -f '/pro/local/bin/git-diff-files' && ln '/pro/local/bin/git' '/pro/local/bin/git-diff-files' ; rm -f '/pro/local/bin/git-d iff-index' && ln '/pro/local/bin/git' '/pro/local/bin/git-diff-index' ; rm -f '/pro/local/bin/git-diff-tree' && ln '/pro/local/bin/git' '/pro/local/bin/git-diff-tree' ; rm -f '/pro/local/! bin/git-fast-export' && ln '/pro/local/bin/git' '/pro/local/bin/git-fast-export' ; rm -f '/pro/local/bin/git-fetch' && ln '/pro/local/bin/git' '/pro/local/bin/git-fetch' ; rm -f '/pro/local/bin/git-fetch-pack' && ln '/pro/local/bin/git' '/pro/local/bin/git-fetch-pack' ; rm -f '/pro/local/bin/git-fetch--tool' && ln '/pro/local/bin/git' '/pro/local/bin/git-fetch--tool' ; rm -f '/pro/local/bin/git-fmt-merge-msg' && ln '/pro/local/bin/git' '/pro/local/bin/git-fmt-merge-msg' ; rm -f '/pro/local/bin/git-for-each-ref' && ln '/pro/local/bin/git' '/pro/local/bin/git-for-each-ref' ; rm -f '/pro/local/bin/git-fsck' && ln '/pro/local/bin/git' '/pro/local/bin/git-fsck' ; rm -f '/pro/local/bin/git-gc' && ln '/pro/local/bin/git' '/pro/local/bin/git-gc' ; rm -f '/pro/local/bin/git-grep' && ln '/p ro/local/bin/git' '/pro/local/bin/git-grep' ; rm -f '/pro/local/bin/git-init-db' && ln '/pro/local/bin/git' '/pro/local/bin/git-init-db' ; rm -f '/pro/local/bin/git-log' && ln '/pro/local! /bin/git' '/pro/local/bin/git-log' ; rm -f '/pro/local/bin/git-ls-fil es' && ln '/pro/local/bin/git' '/pro/local/bin/git-ls-files' ; rm -f '/pro/local/bin/git-ls-tree' && ln '/pro/local/bin/git' '/pro/local/bin/git-ls-tree' ; rm -f '/pro/local/bin/git-ls-remote' && ln '/pro/local/bin/git' '/pro/local/bin/git-ls-remote' ; rm -f '/pro/local/bin/git-mailinfo' && ln '/pro/local/bin/git' '/pro/local/bin/git-mailinfo' ; rm -f '/pro/local/bin/git-mailsplit' && ln '/pro/local/bin/git' '/pro/local/bin/git-mailsplit' ; rm -f '/pro/local/bin/git-merge-base' && ln '/pro/local/bin/git' '/pro/local/bin/git-merge-base' ; rm -f '/pro/local/bin/git-merge-file' && ln '/pro/local/bin/git' '/pro/local/bin/git-merge-file' ; rm -f '/pro/local/bin/git-merge-ours' && ln '/pro/local/bin/git' '/pro/local/bin/git-merge-ours' ; rm -f '/pro/local/bin/git-mv' && ln '/pro/local/bi n/git' '/pro/local/bin/git-mv' ; rm -f '/pro/local/bin/git-name-rev' && ln '/pro/local/bin/git' '/pro/local/bin/git-name-rev' ; rm -f '/pro/local/bin/git-pack-objects' && ln '/pro/local/b! in/git' '/pro/local/bin/git-pack-objects' ; rm -f '/pro/local/bin/git-prune' && ln '/pro/local/bin/git' '/pro/local/bin/git-prune' ; rm -f '/pro/local/bin/git-prune-packed' && ln '/pro/local/bin/git' '/pro/local/bin/git-prune-packed' ; rm -f '/pro/local/bin/git-push' && ln '/pro/local/bin/git' '/pro/local/bin/git-push' ; rm -f '/pro/local/bin/git-read-tree' && ln '/pro/local/bin/git' '/pro/local/bin/git-read-tree' ; rm -f '/pro/local/bin/git-reflog' && ln '/pro/local/bin/git' '/pro/local/bin/git-reflog' ; rm -f '/pro/local/bin/git-send-pack' && ln '/pro/local/bin/git' '/pro/local/bin/git-send-pack' ; rm -f '/pro/local/bin/git-config' && ln '/pro/local/bin/git' '/pro/local/bin/git-config' ; rm -f '/pro/local/bin/git-rerere' && ln '/pro/local/bin/git' '/pro/local/bin/git-rerere' ; rm -f '/pro/local/bin/git-reset' && ln '/pro/local/bin/git' '/pro/local/bin/git-reset' ; rm -f '/pro/local/bin/git-rev-list' && ln '/pro/local/bin/git' '/pro/local/bin/git-rev-list' ; rm ! -f '/pro/local/bin/git-rev-parse' && ln '/pro/local/bin/git' '/pro/loc al/bin/git-rev-parse' ; rm -f '/pro/local/bin/git-revert' && ln '/pro/local/bin/git' '/pro/local/bin/git-revert' ; rm -f '/pro/local/bin/git-rm' && ln '/pro/local/bin/git' '/pro/local/bin/git-rm' ; rm -f '/pro/local/bin/git-shortlog' && ln '/pro/local/bin/git' '/pro/local/bin/git-shortlog' ; rm -f '/pro/local/bin/git-show-branch' && ln '/pro/local/bin/git' '/pro/local/bin/git-show-branch' ; rm -f '/pro/local/bin/git-stripspace' && ln '/pro/local/bin/git' '/pro/local/bin/git-stripspace' ; rm -f '/pro/local/bin/git-symbolic-ref' && ln '/pro/local/bin/git' '/pro/local/bin/git-symbolic-ref' ; rm -f '/pro/local/bin/git-tag' && ln '/pro/local/bin/git' '/pro/local/bin/git-tag' ; rm -f '/pro/local/bin/git-tar-tree' && ln '/pro/local/bin/git' '/pro/local/bin/git-tar-tree' ; rm -f '/pro/loc al/bin/git-unpack-objects' && ln '/pro/local/bin/git' '/pro/local/bin/git-unpack-objects' ; rm -f '/pro/local/bin/git-update-index' && ln '/pro/local/bin/git' '/pro/local/bin/git-update-in! dex' ; rm -f '/pro/local/bin/git-update-ref' && ln '/pro/local/bin/git' '/pro/local/bin/git-update-ref' ; rm -f '/pro/local/bin/git-upload-archive' && ln '/pro/local/bin/git' '/pro/local/bin/git-upload-archive' ; rm -f '/pro/local/bin/git-verify-pack' && ln '/pro/local/bin/git' '/pro/local/bin/git-verify-pack' ; rm -f '/pro/local/bin/git-verify-tag' && ln '/pro/local/bin/git' '/pro/local/bin/git-verify-tag' ; rm -f '/pro/local/bin/git-write-tree' && ln '/pro/local/bin/git' '/pro/local/bin/git-write-tree' ; rm -f '/pro/local/bin/git-show-ref' && ln '/pro/local/bin/git' '/pro/local/bin/git-show-ref' ; rm -f '/pro/local/bin/git-pack-refs' && ln '/pro/local/bin/git' '/pro/local/bin/git-pack-refs' ; -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 13:32 ` H.Merijn Brand @ 2007-12-18 14:03 ` Jakub Narebski 2007-12-18 14:27 ` H.Merijn Brand 0 siblings, 1 reply; 12+ messages in thread From: Jakub Narebski @ 2007-12-18 14:03 UTC (permalink / raw) To: H.Merijn Brand; +Cc: Andy Dougherty, git On Tue, 18 Dec 2007, H.Merijn Brand wrote: > On Tue, 18 Dec 2007 13:32:59 +0100, Jakub Narebski <jnareb@gmail.com> wrote: >> H.Merijn Brand wrote: >>> On Tue, 18 Dec 2007 10:14:38 +0100, Jakub Narebski <jnareb@gmail.com> wrote: >>>> >>>> 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? > > No. I reported this before, but not to the list. This is why I created > my own make-install shell: I though that you were talking about _default_ 'install' program (first in PATH). Is /opt/imake/bin/install used below? I have forgot to tell that beside uncommenting AC_PROG_INSTALL line in configure.ac (and doing "make configure") you have to also uncomment the "INSTALL = @INSTALL@" in config.mak.in for "make install" to use install program found by ./configure script. > /pro/3gl/LINUX/git-2007-12-17 113> make install > SUBDIR git-gui > INDEX lib/ > SUBDIR gitk-git > make[1]: Nothing to be done for `all'. > SUBDIR perl > SUBDIR templates > install -d -m 755 '/pro/local/bin' > rm: /pro/local/bin/ directory > Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 > mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 > mv [-f] [-i] [-e warn|force|ignore] d1 d2 Strange... By the way, I have took a look at hos ./configure script chooses which 'install' to use, and at least for GNU Autoconf 2.59 it does not talk about HP-UX at all, and checks binaries to reject by grepping for a string, instead of checking if it install files correctly using some script (at least checking if it install files and creates directories, and accepts install options used, without checking for correct permissions and group, etc.). Relevant fragment of generated ./configure script -- >8 -- configure # Find a good install program. We prefer a C program (faster), # so one script is as good as another. But avoid the broken or # incompatible versions: # SysV /etc/install, /usr/sbin/install # SunOS /usr/etc/install # IRIX /sbin/install # AIX /bin/install # AmigaOS /C/install, which installs bootblocks on floppy discs # AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag # AFS /usr/afsws/bin/install, which mishandles nonexistent args # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" # OS/2's system install, which has a completely different semantic # ./install, which can be erroneously created by make from ./install.sh. echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6 if test -z "$INSTALL"; then if test "${ac_cv_path_install+set}" = set; then echo $ECHO_N "(cached) $ECHO_C" >&6 else as_save_IFS=$IFS; IFS=$PATH_SEPARATOR for as_dir in $PATH do IFS=$as_save_IFS test -z "$as_dir" && as_dir=. # Account for people who put trailing slashes in PATH elements. case $as_dir/ in ./ | .// | /cC/* | \ /etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \ ?:\\/os2\\/install\\/* | ?:\\/OS2\\/INSTALL\\/* | \ /usr/ucb/* ) ;; *) # OSF1 and SCO ODT 3.0 have their own names for install. # Don't use installbsd from OSF since it installs stuff as root # by default. for ac_prog in ginstall scoinst install; do for ac_exec_ext in '' $ac_executable_extensions; do if $as_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then if test $ac_prog = install && grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then # AIX install. It has an incompatible calling convention. : elif test $ac_prog = install && grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then # program-specific install script used by HP pwplus--don't use. : else ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" break 3 fi fi done done ;; esac done fi if test "${ac_cv_path_install+set}" = set; then INSTALL=$ac_cv_path_install else # As a last resort, use the slow shell script. We don't cache a # path for INSTALL within a source directory, because that will # break other packages using the cache if that directory is # removed, or if the path is relative. INSTALL=$ac_install_sh fi fi echo "$as_me:$LINENO: result: $INSTALL" >&5 echo "${ECHO_T}$INSTALL" >&6 -- Jakub Narebski Poland ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 14:03 ` Jakub Narebski @ 2007-12-18 14:27 ` H.Merijn Brand 0 siblings, 0 replies; 12+ messages in thread From: H.Merijn Brand @ 2007-12-18 14:27 UTC (permalink / raw) To: Jakub Narebski; +Cc: Andy Dougherty, git On Tue, 18 Dec 2007 15:03:09 +0100, Jakub Narebski <jnareb@gmail.com> wrote: > On Tue, 18 Dec 2007, H.Merijn Brand wrote: > > On Tue, 18 Dec 2007 13:32:59 +0100, Jakub Narebski <jnareb@gmail.com> wrote: > >> H.Merijn Brand wrote: > >>> On Tue, 18 Dec 2007 10:14:38 +0100, Jakub Narebski <jnareb@gmail.com> wrote: > >>>> > >>>> 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? > > > > No. I reported this before, but not to the list. This is why I created > > my own make-install shell: > > I though that you were talking about _default_ 'install' program > (first in PATH). Is /opt/imake/bin/install used below? Yes. There is only ONE install program (that is a small lie, there is also /usr/sbin/install, but that is not accessible for mortal users) > I have forgot to tell that beside uncommenting AC_PROG_INSTALL line > in configure.ac (and doing "make configure") you have to also uncomment > the "INSTALL = @INSTALL@" in config.mak.in for "make install" to use > install program found by ./configure script. But I don't think it found install-sh. /pro/3gl/LINUX/git-2007-12-17 103 > grep -w install config-log checking for a BSD-compatible install... /opt/imake/bin/install -c > > /pro/3gl/LINUX/git-2007-12-17 113> make install > > SUBDIR git-gui > > INDEX lib/ > > SUBDIR gitk-git > > make[1]: Nothing to be done for `all'. > > SUBDIR perl > > SUBDIR templates > > install -d -m 755 '/pro/local/bin' > > rm: /pro/local/bin/ directory > > Usage: mv [-f] [-i] [-e warn|force|ignore] f1 f2 > > mv [-f] [-i] [-e warn|force|ignore] f1 ... fn d1 > > mv [-f] [-i] [-e warn|force|ignore] d1 d2 > > Strange... > > By the way, I have took a look at hos ./configure script chooses which > 'install' to use, and at least for GNU Autoconf 2.59 it does not talk > about HP-UX at all, and checks binaries to reject by grepping for > a string, instead of checking if it install files correctly using some > script (at least checking if it install files and creates directories, > and accepts install options used, without checking for correct permissions > and group, etc.). > > Relevant fragment of generated ./configure script http://www.xs4all.nl/~procura/configure added a 'set -x' there: configure: CHECKS for programs checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed + echo configure:2219: checking for a BSD-compatible install + 1>& 5 + echo checking for a BSD-compatible install... \c + 1>& 6 checking for a BSD-compatible install... + test -z + test = set + as_save_IFS= + IFS=: + IFS= + test -z . + IFS= + test -z /u/usr/merijn/bin/private + test -f /u/usr/merijn/bin/private/ginstall + test -f /u/usr/merijn/bin/private/scoinst + test -f /u/usr/merijn/bin/private/install + IFS= etc etc for the rest of the $PATH ... + test -z /opt/imake/bin + test -f /opt/imake/bin/ginstall + test -f /opt/imake/bin/scoinst + test -f /opt/imake/bin/install + test install = install + grep dspmsg /opt/imake/bin/install + 1> /dev/null 2>& 1 + test install = install + grep pwplus /opt/imake/bin/install + 1> /dev/null 2>& 1 + ac_cv_path_install=/opt/imake/bin/install -c + break 3 + test set = set + INSTALL=/opt/imake/bin/install -c + echo configure:2274: result: /opt/imake/bin/install -c + 1>& 5 + echo /opt/imake/bin/install -c + 1>& 6 /opt/imake/bin/install -c + exit + exit_status=0 + 1>& 5 + echo + cat + 0< /var/tmp/sh8180.20 + echo + 2>& 1 + 2>& 1 + sed -n s/'/'\\''/g; s/^\([_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*_cv_[_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]*\)=\(.*\)/\1='\2'/p + echo + cat + 0< /var/tmp/sh8180.21 + echo + sort + echo SHELL + eval ac_val=$SHELL : : + ac_val=o + echo OBJEXT='o' + echo INSTALL_PROGRAM + eval ac_val=$INSTALL_PROGRAM + ac_val= + echo INSTALL_PROGRAM='' + echo INSTALL_SCRIPT + eval ac_val=$INSTALL_SCRIPT + ac_val= + echo INSTALL_SCRIPT='' + echo INSTALL_DATA + eval ac_val=$INSTALL_DATA + ac_val= + echo INSTALL_DATA='' + echo AR + eval ac_val=$AR : : + echo + test -n + test -s confdefs.h + cat + 0< /var/tmp/sh8180.23 + echo + sed /^$/d confdefs.h + sort + echo + test 0 != 0 + echo configure: exit 0 + rm -f core *.core + rm -rf conftest* confdefs.h conf8180* > -- >8 -- configure > > # Find a good install program. We prefer a C program (faster), > # so one script is as good as another. But avoid the broken or > # incompatible versions: > # SysV /etc/install, /usr/sbin/install > # SunOS /usr/etc/install > # IRIX /sbin/install > # AIX /bin/install > # AmigaOS /C/install, which installs bootblocks on floppy discs > # AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag > # AFS /usr/afsws/bin/install, which mishandles nonexistent args > # SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff" > # OS/2's system install, which has a completely different semantic > # ./install, which can be erroneously created by make from ./install.sh. > echo "$as_me:$LINENO: checking for a BSD-compatible install" >&5 > echo $ECHO_N "checking for a BSD-compatible install... $ECHO_C" >&6 > if test -z "$INSTALL"; then > if test "${ac_cv_path_install+set}" = set; then > echo $ECHO_N "(cached) $ECHO_C" >&6 > else > as_save_IFS=$IFS; IFS=$PATH_SEPARATOR > for as_dir in $PATH > do > IFS=$as_save_IFS > test -z "$as_dir" && as_dir=. > # Account for people who put trailing slashes in PATH elements. > case $as_dir/ in > ./ | .// | /cC/* | \ > /etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \ > ?:\\/os2\\/install\\/* | ?:\\/OS2\\/INSTALL\\/* | \ > /usr/ucb/* ) ;; > *) > # OSF1 and SCO ODT 3.0 have their own names for install. > # Don't use installbsd from OSF since it installs stuff as root > # by default. > for ac_prog in ginstall scoinst install; do > for ac_exec_ext in '' $ac_executable_extensions; do > if $as_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then > if test $ac_prog = install && > grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then > # AIX install. It has an incompatible calling convention. > : > elif test $ac_prog = install && > grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then > # program-specific install script used by HP pwplus--don't use. > : > else > ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c" > break 3 > fi > fi > done > done > ;; > esac > done > > > fi > if test "${ac_cv_path_install+set}" = set; then > INSTALL=$ac_cv_path_install > else > # As a last resort, use the slow shell script. We don't cache a > # path for INSTALL within a source directory, because that will > # break other packages using the cache if that directory is > # removed, or if the path is relative. > INSTALL=$ac_install_sh > fi > fi > echo "$as_me:$LINENO: result: $INSTALL" >&5 > echo "${ECHO_T}$INSTALL" >&6 > -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11, & 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org http://mirrors.develooper.com/hpux/ http://www.test-smoke.org http://www.goldmark.org/jeff/stupid-disclaimers/ ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH] Explain what 'ginstall' is 2007-12-18 1:21 ` Jakub Narebski 2007-12-18 7:38 ` H.Merijn Brand @ 2007-12-23 9:01 ` Jan Hudec 1 sibling, 0 replies; 12+ messages in thread From: Jan Hudec @ 2007-12-23 9:01 UTC (permalink / raw) To: Jakub Narebski; +Cc: Andy Dougherty, git On Mon, Dec 17, 2007 at 17:21:08 -0800, 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... What's wrong with the one that comes with automake? It should be portable the insane way ./configure script is -- which should be at least as much as git -- and the license is compatible (MIT/X). > Footnotes: > ---------- > [*1*] By "portable" I mean here 'git portable', i.e. requiring only > those shell constructs/features that git require, not necessary > insanelt portable the way ./configure script is. -- Jan 'Bulb' Hudec <bulb@ucw.cz> ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2007-12-23 9:02 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
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).