Bug#643341: [pkg-gnupg-maint] Bug#643341: Bug#643341: libgpg-error-dev: cross-compiling anything based on libgpg-error is painful

2018-10-18 Thread NIIBE Yutaka
Simon McVittie wrote: > The multiarch tuple used to form ${libdir} on Debian is not always > identical to the GNU host. [...] > There's a Debian-specific option "gcc -print-multiarch" added by a > Debian patch, although not all of our compilers have a similar patch > (gcc does but clang doesn't).

Bug#643341: [pkg-gnupg-maint] Bug#643341: Bug#643341: libgpg-error-dev: cross-compiling anything based on libgpg-error is painful

2018-10-17 Thread Simon McVittie
On Wed, 17 Oct 2018 at 14:31:50 +0900, NIIBE Yutaka wrote: > At configure time, if it detects libdir for multiarch, it lets > gpg-error-config script architecture independent to dynamically define > PKG_CONFIG_LIBDIR (by CC or gcc -dumpmachine). The multiarch tuple used to form ${libdir} on Debian

Bug#643341: [pkg-gnupg-maint] Bug#643341: Bug#643341: libgpg-error-dev: cross-compiling anything based on libgpg-error is painful

2018-10-16 Thread NIIBE Yutaka
Hello, again, Simon McVittie wrote: > For Debian, I wonder whether we might be able to patch the script to > remove this part, which looks like the only architecture variation: > > prefix=@prefix@ > exec_prefix=@exec_prefix@ > libdir=${PKG_CONFIG_LIBDIR:-@libdir@} > PKG_CONFIG_PAT

Bug#643341: [pkg-gnupg-maint] Bug#643341: Bug#643341: libgpg-error-dev: cross-compiling anything based on libgpg-error is painful

2018-10-16 Thread Werner Koch
On Tue, 16 Oct 2018 09:51, s...@debian.org said: > However, none of this solves co-installability in Debian: > libgpg-error-dev:amd64 and libgpg-error-dev:armhf can't be > installed at the same time, because they have different content in > /usr/bin/gpg-error-config, and that will be a problem for