Re: Building git 2.4.5 on AIX 6.1 problems
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 11, 2015, 06:57 UTC
- Message-ID
- <CAPc5daWJ7T9UFi_457MvTBN7hoxAD0mEwwbQE1R076=Z+BWu7w@mail.gmail.com>
- In-Reply-To
- <1436596266437-7635513.post@n2.nabble.com>
On Fri, Jul 10, 2015 at 11:31 PM, norricorp <john@norricorp.f9.co.uk> wrote:
Show 32 quoted lines
>
> This is the output I got from using V=1 with make
> gcc -g -O2 -I. -D_LARGE_FILES -DNO_D_TYPE_IN_DIRENT -DNO_NSEC -DOLD_ICONV
> -pthread -DHAVE_PATHS_H -DHAVE_
> LIBCHARSET_H -DHAVE_STRINGS_H -DSHA1_HEADER='<openssl/sha.h>'
> -DFREAD_READS_DIRECTORIES -DNO_STRCASESTR -
> DNO_STRLCPY -Icompat/fnmatch -DNO_FNMATCH_CASEFOLD -DUSE_WILDMATCH
> -DNO_MKSTEMPS -DINTERNAL_QSORT -Icompat
> /regex -DDEFAULT_PAGER='"more"' -DSHELL_PATH='"/bin/sh"' -o
> git-credential-store credential-store.o libg
> it.a xdiff/lib.a -lz -liconv -lintl -lcrypto -pthread
>
> Also, the undefined symbol errors - does anyone know which library these are
> supposed to be in?
> So when I grep for one undefined symbol
> $: git-2.4.5 $ grep -R diff_queued_diff *
> builtin/blame.c: if (!diff_queued_diff.nr) {
> builtin/blame.c: for (i = 0; i < diff_queued_diff.nr; i++) {
> builtin/blame.c: p = diff_queued_diff.queue[i];
> ......
> builtin/diff.c: diff_queue(&diff_queued_diff, one, two);
> builtin/fast-export.c: for (i = 0; i < diff_queued_diff.nr; i++)
> builtin/fast-export.c: if
> (!S_ISGITLINK(diff_queued_diff.queue[i]->two->mode))
> builtin/fast-export.c:
> export_blob(diff_queued_diff.queue[i]->two->sha1);
> ........
> diff.c: struct diff_queue_struct *q = &diff_queued_diff;
> diff.c: struct diff_queue_struct *q = &diff_queued_diff;
>
> 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...