On Sun, Dec 02, 2018 at 10:43:51PM -0800, John Horigan wrote:
> You filed a bug on a package that I maintain, libagg-dev. I'm in the
> process of updating the package with your patch and I want to make sure it
> cross-compiles before I ask my sponsor to upload it. I get a lintian
Thank you!
> warning about the pkgconfig file being installed in /usr/lib instead of
> /usr/share. Is this a serious issue for cross compilation?
The answer is "yes and no". The placement of your .pc file is not a
problem to cross building src:agg at all. It very much is a problem for
cross compiling reverse dependencies of libagg-dev that want to use
libagg.pc as they will be unable to find it. Placing it in /usr/share is
theoretically possible here, but it may be confusing. Consider
installing libagg-dev for amd64 and the asking i686-linux-gnu-pkg-config
for libagg. It'll happily report libagg to be available even though it
is not usable. It would be far better to error out here. Therefore you
should install it to /usr/lib/$DEB_HOST_MULTIARCH/pkgconfig. The easiest
way of doing so is passing
--libdir='${prefix}/lib/'"$DEB_HOST_MULTIARCH" to configure and
dh_auto_configure does that for you already (given a sufficiently high
compat level). My FTCBFS patch passes --libdir=/usr/lib to revert
dh_auto_configure's flag. Dropping that flag and updating the .install
files should be enough here. Once you do that, you may also consider
marking libagg-dev Multi-Arch: same (if no shared files differ).
Hope this helps
Helmut
