On 2020-04-15 00:02 +0200, Hilmar Preuße wrote: > Hi, > > I'm pretty sure this is a dumb question. I'm using sbuild to cross > compile packages, e.g. texlive-bin. This works fine for release arches. > Now I try to build for a non-release arch like this: > > sbuild --host=sparc64 -d unstable --extra-repository='deb > http://ftp.de.debian.org/debian-ports unstable main' > --extra-repository-key=/usr/share/keyrings/debian-ports-archive-keyring.gpg > texlive-bin > > The build fails, the build log tells me that some B/D's could not be > fulfilled. However I know that the packages in question do exist for > that arch. What am I missing?
It's because libc6 is out of date on sparc64 compared to amd64 (the arch I
assume you are building on)
(unstable-amd64-clean-home)wookey@e110476-lin:~$apt policy libc6-dev:sparc64
libc6-dev:sparc64:
Installed: (none)
Candidate: 2.30-2+sparc64
Version table:
2.30-2+sparc64 500
500 http://ftp.de.debian.org/debian-ports unstable/main sparc64 Packages
-bash: __git_ps1: command not found
(unstable-amd64-clean-home)wookey@e110476-lin:~$ apt policy libc6-dev
libc6-dev:
Installed: 2.30-4
Candidate: 2.30-4
Version table:
*** 2.30-4 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
-bash: __git_ps1: command not found
you can't install mismatched versions of libc6 so none of the
cross-dependencies will install. Once glibc 2.30-4 is built on sparc64
theings should work (so long as no other libraries are
version-skewed).
Building in testing is one way to avoid this problem, if that's any use to you.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
signature.asc
Description: PGP signature
