From: Pavel Roskin <proski@gnu.org>
To: Michal Rokos <michal.rokos@nextsoft.cz>
Cc: git@vger.kernel.org
Subject: Re: git on HP-UX
Date: Thu, 06 Jul 2006 10:53:49 -0400 [thread overview]
Message-ID: <1152197629.7720.10.camel@dv> (raw)
In-Reply-To: <200607060950.34558.michal.rokos@nextsoft.cz>
Hello!
On Thu, 2006-07-06 at 09:50 +0200, Michal Rokos wrote:
> Hello,
>
> I needed following changes in order to make git compile on HP-UX:
> +ifeq ($(uname_S),HP-UX)
> + NO_IPV6 = YesPlease
> + NO_CURL = YesPlease
Is there any fundamental problem with curl and IPv6 on HP-UX? I don't
think so.
Sorry for using your path as a bad example, but the appearance of such
patches is a perfect argument for a real configure script. If we
continue patching Makefile, we'll drown in such conditionals. And the
worst thing is, nobody without access to an HP-UX system will know why
IPv6 isn't working there. Makefile will become a pile of code that
cannot be easily verified for correctness.
Autoconf based tests can actually test if certain code can be compiled
and linked. If HP-UX fixed IPv6, the test would enable it. If some
genius manages to compile curl on HP-UX, http support will be enabled on
that machine with no manual changes in Makefile.
I hope the Autoconf based configure is on its way to git, but I don't
see in in the "pu" branch yet. I'm not very keen about reinventing
Autoconf and hacking a hand-made configure script.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-07-06 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 7:50 git on HP-UX Michal Rokos
2006-07-06 14:53 ` Pavel Roskin [this message]
2006-07-07 0:20 ` Junio C Hamano
2006-07-08 7:38 ` Pavel Roskin
2006-07-09 22:23 ` Petr Baudis
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=1152197629.7720.10.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=michal.rokos@nextsoft.cz \
/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).