From: Andy Dougherty <doughera@lafayette.edu>
To: git@vger.kernel.org
Subject: [PATCH] Explain what 'ginstall' is
Date: Mon, 17 Dec 2007 16:46:09 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0712171641370.24957@fractal.phys.lafayette.edu> (raw)
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
next reply other threads:[~2007-12-17 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:46 Andy Dougherty [this message]
2007-12-18 1:21 ` [PATCH] Explain what 'ginstall' is 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
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=Pine.LNX.4.64.0712171641370.24957@fractal.phys.lafayette.edu \
--to=doughera@lafayette.edu \
--cc=git@vger.kernel.org \
/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).