> $ wget
> http://deb.debian.org/debian/pool/main/m/mariadb-10.5/libmariadbd-dev_10.5.5-1_amd64.deb
> ...
> $ wget
> http://deb.debian.org/debian/pool/main/m/mariadb-10.5/libmariadbd-dev_10.5.5-1_arm64.deb
> ...
> $ dpkg-deb -x libmariadbd-dev_10.5.5-1_amd64.deb amd64
> $ dpkg-deb -x libmariadbd-dev_10.5.5-1_arm64.deb arm64
> $ diff -u a*64/usr/include/mariadb/server/my_config.h
> --- amd64/usr/include/mariadb/server/my_config.h 2020-09-25
> 18:56:59.000000000 +0200
> +++ arm64/usr/include/mariadb/server/my_config.h 2020-09-25
> 18:56:59.000000000 +0200
$ diff -u a*64/usr/include/mariadb/server/my_config.h | diffstat
my_config.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
OK, so they have custom contents based on arch, but just that header
file, nothing else.
> The usual solution to fix this is moving the header to a multiarch
> location (i.e. below /usr/include/${DEB_HOST_MULTIARCH}).
If I move just the header file but not all of
/usr/include/mariadb/server, will there be issues with paths at some
point?
I don't have any sample program to build and test against
libmariadbd-dev and I am not a C/C++ coder so this starts to be beyond
my level.
