From: Perry Smith <pedzsan@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Mike Ralphson <mike.ralphson@gmail.com>,
git@vger.kernel.org
Subject: Re: git 1.6.1 on AIX 5.3
Date: Wed, 28 Jan 2009 09:03:23 -0600 [thread overview]
Message-ID: <87325FCF-CD16-43CE-9CD0-CAC73904903A@gmail.com> (raw)
In-Reply-To: <20090128074204.GA31951@coredump.intra.peff.net>
On Jan 28, 2009, at 1:42 AM, Jeff King wrote:
> On Tue, Jan 27, 2009 at 11:37:21PM -0800, Junio C Hamano wrote:
>
>>>> Just to be sure we are on the same page. My directory structure
>>>> has a
>>>> top/src/git-1.6.1 and top/build/git.1.6.1. The src/git-1.6.1 is
>>>> the
>>>> tar ball. The build/git-1.6.1 starts out empty. I cd into it and
>>>> then do: ../../src/git-1.6.1/configure <options> After this
>>>> completes, you can do "make".
>>>
>>> I don't see how this would work without automake support, which
>>> git does
>>> not have.
>>
>> ... nor want to have ;-).
>
> Heh. Yes, in case there was any confusion: I don't want my statement
> in
> any way to be construed as a suggestion to support automake.
>
> I would not be opposed to it if it somehow enhanced some users'
> experience without bothering people who didn't want to touch it (like
> the way that autoconf support is implemented). But I don't see how
> that
> would be possible.
Thats fine. I didn't know if this was a "known" situation or not so I
just mentioned it.
As I mentioned, most open source code supports this style of build. I
have no idea
what it would take to get it to work.
next prev parent reply other threads:[~2009-01-28 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 20:02 git 1.6.1 on AIX 5.3 Perry Smith
2009-01-26 21:00 ` Jeff King
2009-01-26 22:32 ` Mike Ralphson
2009-01-26 22:57 ` Perry Smith
2009-01-27 3:52 ` Jeff King
2009-01-27 10:10 ` Mike Ralphson
2009-01-28 1:35 ` Perry Smith
2009-01-28 7:01 ` Jeff King
2009-01-28 7:37 ` Junio C Hamano
2009-01-28 7:42 ` Jeff King
2009-01-28 15:03 ` Perry Smith [this message]
2009-01-28 9:48 ` Mike Ralphson
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=87325FCF-CD16-43CE-9CD0-CAC73904903A@gmail.com \
--to=pedzsan@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mike.ralphson@gmail.com \
--cc=peff@peff.net \
/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).