Re: bzip 2 fails to build on IRIX 6.5

[Roland Illig <roland.illig%gmx.de@localhost>]

Am 08.09.2019 um 12:25 schrieb Mark Kirby:
> libtool: link: gcc -shared  -DPIC  .libs/blocksort.o .libs/bzlib.o
> .libs/compress.o .libs/crctable.o .libs/decompress.o .libs/huffman.o
> .libs/randtable.o   -L/build/archivers/bzip2/work/.buildlink/lib
> -Wl,-R/usr/pkg/lib -O2   -Wl,-soname -Wl,libbz2.so.1 `test -n
> "sgi1.0" && func_echo_all "-Wl,-set_version -Wl,sgi1.0"`
> -Wl,-update_registry -Wl,.libs/so_locations -o .libs/libbz2.so.1.0

> /opt/local/gcc-8.2.0/lib/gcc/mips-sgi-irix6.5/8.2.0/../../../../mips-sgi-irix6.5/bin/ld:
> sgi1.0: No such file: No such file or directory

The output from WRKSRC/.work.log looks good to me. Maybe there's
something wrong with your local GCC installation. The ld command should
be able to interpret the -set_version option, but that seems not to be
the case here.

The next step is to see how gcc calls ld. To see this, run:

    bmake build-env
    grep '^<.> .*/gcc' ../.work.log | tail -n 1

Add the -v option to the gcc command, and re-run it. This should reveal
the command line to the failing ld. I expect that the ld command line
contains "-set_version sgi1.0", and that looks completely valid to me. I
wonder what it really looks like.

Roland