Bug#843111: llvm-toolchain-3.7: FTBFS on i386
Hi, > Moving GHC 8 to LLVM 3.8 would be possible with some minor patches from > upstream, though the lack of LLVM 3.8 on armel would be a big problem. Also > I'm > not sure the GHC maintainers want to deviate from upstream on the LLVM > version. > But we can move to 3.7 and drop 3.5 for now, then after that has happened, > consider if we can move to 3.8 and what we do with armel. > what about shipping llvm 3.7 only for arch:all, arm64, armel and armhf? this way we can remove it from mostly everywhere and let it migrate without caring of i386 and amd64 anymore. Does this sound crazy? G. signature.asc Description: OpenPGP digital signature
Bug#843111: llvm-toolchain-3.7: FTBFS on i386
Hi Sylvestre, On 04/11/16 09:46, Sylvestre Ledru wrote: > Le 04/11/2016 à 00:02, Emilio Pozuelo Monfort a écrit : >> Source: llvm-toolchain-3.7 >> Version: 1:3.7.1-3 >> Severity: serious >> >> Hi, >> >> Your package failed to build on i386. We need llvm 3.7 in testing/stretch >> for ghc 8 (then we can remove llvm 3.5), thus opening this bug. > I wish I can remove 3.7 from the next stable to have two releases (3.8 & 3.9). > Any chance this could happen on your side? GHC needs LLVM on armel/armhf/arm64. ghc 7.10.3 (the version currently in testing) uses LLVM 3.5, and GHC 8 (the one in unstable) uses LLVM 3.7. So this would allow us to remove LLVM 3.5, which is in testing at the moment for GHC. Moving GHC 8 to LLVM 3.8 would be possible with some minor patches from upstream, though the lack of LLVM 3.8 on armel would be a big problem. Also I'm not sure the GHC maintainers want to deviate from upstream on the LLVM version. But we can move to 3.7 and drop 3.5 for now, then after that has happened, consider if we can move to 3.8 and what we do with armel. Cheers, Emilio
Bug#843111: llvm-toolchain-3.7: FTBFS on i386
Le 04/11/2016 à 00:02, Emilio Pozuelo Monfort a écrit : Source: llvm-toolchain-3.7 Version: 1:3.7.1-3 Severity: serious Hi, Your package failed to build on i386. We need llvm 3.7 in testing/stretch for ghc 8 (then we can remove llvm 3.5), thus opening this bug. I wish I can remove 3.7 from the next stable to have two releases (3.8 & 3.9). Any chance this could happen on your side? Thanks S
Bug#843111: llvm-toolchain-3.7: FTBFS on i386
Source: llvm-toolchain-3.7 Version: 1:3.7.1-3 Severity: serious Hi, Your package failed to build on i386. We need llvm 3.7 in testing/stretch for ghc 8 (then we can remove llvm 3.5), thus opening this bug. Cheers, Emilio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)