[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ncurses and pkgconfig install location

From: Thomas Dickey
Subject: Re: ncurses and pkgconfig install location
Date: Tue, 16 Nov 2021 15:21:53 -0500
User-agent: Mutt/1.10.1 (2018-07-13)

On Tue, Nov 16, 2021 at 01:17:05PM +0000, Ross Burton wrote:
> On Tue, 16 Nov 2021 at 12:23, Thomas Dickey <dickey@his.com> wrote:
> > > logic to replace what practically every other package does with just
> > > pkgconfigdir=${libdir}/pkgconfig.  What problems does this logic solve
> > > that simply using libdir is the wrong answer for?
> >
> > among other reasons:
> >
> > https://wiki.debian.org/Multiarch/Implementation
> I'm confused then.  That is mostly implemented by passing --libdir and
> expecting software to respect it:
> "most upstream build systems (such as autoconf, with --libdir) will
> install shared libraries, support files, and various development files
> (such as static libraries and .so symlinks) together to the same
> target directory."
> For example, libxml2 is multiarch, so has its shared library in
> /usr/lib/x86_64-linux-gnu in the amd64 build:
> https://packages.debian.org/sid/amd64/libxml2/filelist
> And the pkgconfig file is simply installed to $libdir/pkgconfig:
> https://packages.debian.org/sid/amd64/libxml2-dev/filelist
> libxml2 just uses $libdir to install the pkgconfig files:
> https://gitlab.gnome.org/GNOME/libxml2/-/blob/master/Makefile.am#L1267
> How is libxml2 doing something wrong?

It's not.  I had forgotten that in the process of setting up non-conflicting
test-packages, I'd left my .so's in /usr/lib.

(On other systems, I have other workarounds).

sure, I can make the default $libdir/pkgconfig

Thomas E. Dickey <dickey@invisible-island.net>

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]