Re: Bug 2171

On Mon, Mar 09, 2015 at 10:57:07PM +0000, Steve Fryatt wrote:
>
> Thanks -- I think I can see what's supposed to be happening now. It appears
> to be libnsutils, which despite giving the following output when built
>
> steve@castlerigg:~/Development/NetSurf/workspace/libnsutils$ make
> TARGET=riscos install
> COMPILE: src/base64.c
> COMPILE: src/time.c
> AR: build-Linux-riscos-release-lib-static/libnsutils.a
> install -m 644 include/nsutils/errors.h
> /home/steve/GCCSDK/env/include/nsutils
> install -m 644 include/nsutils/base64.h
> /home/steve/GCCSDK/env/include/nsutils
> install -m 644 include/nsutils/time.h
> /home/steve/GCCSDK/env/include/nsutils
> sed -e... libnsutils.pc.in >build-Linux-riscos-release-lib-
> static/libnsutils.pc
> install -m 644 build-Linux-riscos-release-lib-static/libnsutils.pc
> /home/steve/GCCSDK/env/lib/pkgconfig/libnsutils.pc
> install -m 644 build-Linux-riscos-release-lib-static/libnsutils.a
> /home/steve/GCCSDK/env/lib
>
> seems not to have actually done anything to libnsutils.pc. Manually
> replacing "LIBRARIES" with "-lnsutils" looks to have made things happy
> again.

This sounds very much as if you need to upgrade to the latest
buildsystem -- it is responsible for substituting the correct value for
LIBRARIES when generating the pkgconfig output.


J.