Bug#1000724: libapr1-dev: Enable cross-build Multi-Arch

Stefan Fritsch <[email protected]> Wed, 5 Nov 2025 21:58:14 +0100
Newsgroups gmane.linux.debian.devel.apache
Message-ID <b6a6884c-713e-4793-b44c-855ec0afe9c9__31409.7472628177$1762376367$gmane$org@sfritsch.de>
Hi,

sorry for the late response.

Am 27.11.21 um 22:54 schrieb João Rodrigues:
> Package: libapr1-dev
> Version: 1.7.0-6+deb11u1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> I would like to install libapr1-dev and libapr1-dev:armhf side by side,
> since this package is a dependency of liblog4cxx-dev.
> 
> However, I get the message:
>   libapr1-dev : Conflicts: libapr1-dev:armhf but 1.7.0-6+deb11u1 is to be installed
>   libapr1-dev:armhf : Conflicts: libapr1-dev but 1.7.0-6+deb11u1 is to be installed
> 
> While I was not expecting any conflicts.
> 
>  From a cursory glance, it appears that, in addition to the headers
> (which should be similar between architectures, although I haven't
> checked), there are is also a apr-1-config binary, which is different
> between versions.
> Maybe the configuration can be moved to the /usr/lib/*/, leaving
> apr-1-config as a shell script which is equal between versions?
> I think there are no conflicts if the files are equal between different
> architectures.
> (A similar problem also happens in libaprutil1-dev, I don't know if I
> should report this bug also there or not)
At the very least, /usr/include/apr-1.0/apr.h is arch dependent and 
would have to be moved.

/usr/share/apr-1.0/build/apr_rules.mk is also generated during build and 
could therefore also differ between architectures. I think it would take 
some effort to figure out if this can be safely shared or how one could 
make sure that the correct version is used.

Cheers,
Stefan