git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: norricorp <john@norricorp.f9.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: Building git 2.4.5 on AIX 6.1 problems
Date: Sun, 12 Jul 2015 00:18:18 -0400	[thread overview]
Message-ID: <20150712041818.GA17595@peff.net> (raw)
In-Reply-To: <CAPc5daWJ7T9UFi_457MvTBN7hoxAD0mEwwbQE1R076=Z+BWu7w@mail.gmail.com>

On Fri, Jul 10, 2015 at 11:57:28PM -0700, Junio C Hamano wrote:

> > So it is obviously a structure or variable that is being used so does anyone
> > know the library that this is defined in?
> 
> Most of our objects should be found in libgit.a (you can see it on your
> command line) that our Makefile builds.
> 
> Now, it has been more than a decade since I last had to deal with a
> system that needs this the last time, but perhaps AIX linker needs the
> archives explicitly prepared with ranlib(1)? Just a shot in the dark...

Ugh, you are giving me flashbacks. ;)

We use the "s" flag to "ar", which is supposed to do the same thing as
ranlib. But I guess it is possible that the system ar does not respect
that flag. Certainly running ranlib manually would be an interesting
experiment.

If the system has GNU ar on it as well as an AIX ar, it might be
interesting to point $(AR) at the former. E.g.:

  make clean
  make AR=gar

(where "gar" is whatever GNU ar is called on the system).

-Peff

  reply	other threads:[~2015-07-12  4:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 18:06 Building git 2.4.5 on AIX 6.1 problems John Norris
2015-07-09 18:30 ` Junio C Hamano
2015-07-10  4:32   ` John Norris
2015-07-10  5:06     ` Jeff King
2015-07-10  5:09     ` Junio C Hamano
2015-07-11  6:31       ` norricorp
2015-07-11  6:57         ` Junio C Hamano
2015-07-12  4:18           ` Jeff King [this message]
2015-07-13  8:24             ` norricorp
2015-07-16 14:49               ` norricorp

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150712041818.GA17595@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@norricorp.f9.co.uk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).