From: Michael Felt <aixtools@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: build issues on AIX - aka non-GNU environment, no gnu grep, no gcc
Date: Tue, 13 Sep 2016 00:44:29 +0200 [thread overview]
Message-ID: <d746a170-a0b0-cc2a-9d27-f146d872595e@gmail.com> (raw)
In-Reply-To: <xmqqy42wzx1f.fsf@gitster.mtv.corp.google.com>
Try again, reply all this time...
On 12-Sep-16 22:24, Junio C Hamano wrote:
> Michael Felt <aixtools@gmail.com> writes:
>
>> I had a couple of issues when packaging git for AIX
>> a) option -Wall by default - works fine with gcc I am sure, but not so
>> well when gcc is not your compiler
> That is expected. As you said, it is merely "by default" and there
> are mechanisms like config.mak provided for people to override them.
>
>> b) needs a special (GNU) grep argument (-a from memory). This I
>> resolved by downloading and packaging GNU grep. However, I hope this
>> has not introduced a new dependency.
> Read the Makefile and find SANE_TEXT_GREP, perhaps?
Ah - read the manual heh?. Generally, I just download, unpack, and run
configure.
I do not mind needing an extra tool - as long as it is only for the build.
And, since you have something about it in your (still unread) install
Notes - it has not slipped in by accident.
>
> Thanks for helping to spread Git to minority platforms.
The link is: http://www.aixtools.net/index.php/git
I do not use it much (I prefer to package "distributed" src tarballs,
but when testing a potential fix - git can be extremely useful!
All in all, thanks for an easy to port to a "minority" platform!
prev parent reply other threads:[~2016-09-12 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 19:28 build issues on AIX - aka non-GNU environment, no gnu grep, no gcc Michael Felt
2016-09-12 20:24 ` Junio C Hamano
2016-09-12 22:44 ` Michael Felt [this message]
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=d746a170-a0b0-cc2a-9d27-f146d872595e@gmail.com \
--to=aixtools@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).