Hi, On 2019-07-25 18:47, Ximin Luo wrote: > Package: release.debian.org > Severity: normal > > Hi, rustc is currently blocked from migration: > > https://qa.debian.org/excuses.php?package=rustc > > <adsb> no, the issue is > <adsb> Not built on buildd: arch mips binaries uploaded by infinity0 > <adsb> Not built on buildd: arch mipsel binaries uploaded by infinity0 > <kibi> if in doubt → https://release.debian.org/britney/excuses.yaml look for > source: rustc and verdicts for that stanza.
FTR, we are going to remove the mips architecture in the next weeks [1], so the problem will be limited to mipsel soon. [1] https://lists.debian.org/debian-mips/2019/07/msg00010.html > <_rene_> infinity0: can't you make it not built with -g or do -g1 or disable > some features on mipsen? > * _rene_ does the -g1 thingy too, for LO > <_rene_> for anything except amd64 (and i386, but I probably should make it > for i386, too, given I also ignore test suite failures there by now...) > <infinity0> _rene_: i've already tried all of those things > <_rene_> mmh, ok > <infinity0> and various other llvm options, it's detailed in some thread on > pkg-rust-maintainers > > https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2019-January/004844.html > https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2019-January/004887.html > https://github.com/rust-lang/rust/issues/56888 Reducing the number of threads won't help, as the issue there is not the memory available on the buildds (they have 8GB RAM), but the virtual memory address space which on 32-bit mips limits the allocated memory per process to 2GB. Other 32-bit architectures usually have a 3GB limit instead. I wonder how much memory is required to build rustc, if we are just above 2GB, or already close to 3GB. Depending on that we might need to find a solution or add an exception for mipsel only or also for the other 32-bit architectures (armel, armhf, i386). Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
