Hi,
>no, LTS-6 is GHC-7; LTS-7 will be GHC-8. We upload LTS-6 now, get it >into testing (which will require manual intervention for mueval and >lambdabot - any volunteers?) and then look into getting ghc-8 into >unstable, together with LTS-7. indeed, I found it out just after clicking enter key https://www.stackage.org/lts-6.1 >I am ignorant of PIE issues. Can you tell me if this patch should enter >Debian? the issue is: PIE has to be disabled, because it breaks libraries. It is *actually* disabled in Debian, but not in Ubuntu, where it has been enabled by default in the compiler itself (some architectures, not all) gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.3.1-21ubuntu11' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 5.3.1 20160528 (Ubuntu 5.3.1-21ubuntu11) so, when and if pie will be enabled by default in Debian too, this patch will become useful. At this moment you might enable it with something like export CFLAGS="-fpie", to see the breakage (not sure where it breaks, but you shouldn't trust gcc to be built with or without it in any case, so I guess disabling it is the safe option I did import an upstream patch for virtualbox [1] and open bugs against dpkg to inject no-pie by default https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1576915 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823869 maybe doko (in cc) can explain better, I admit I'm clueless on the topic [1] https://sources.debian.net/src/virtualbox/5.0.20-dfsg-2/debian/patches/fix-gcc-pie.patch/ thanks G.
