Skip to content

Instantly share code, notes, and snippets.

@MilhouseVH
Last active August 15, 2016 00:32
Show Gist options
  • Save MilhouseVH/0b98286f016529853b94ee65ac83dda5 to your computer and use it in GitHub Desktop.
Save MilhouseVH/0b98286f016529853b94ee65ac83dda5 to your computer and use it in GitHub Desktop.

** CLEAN BUILD ALERT! **

The following have been built for and runtime tested on RPi, RPi2 and Generic.

Package Old New Changelog
alsa-lib 1.1.1 1.1.2 http://www.alsa-project.org/main/index.php/Changes_v1.1.1_v1.1.2
alsa-utils 1.1.1 1.1.2 http://www.alsa-project.org/main/index.php/Changes_v1.1.1_v1.1.2
elfutils 0.165 0.166 https://git.fedorahosted.org/cgit/elfutils.git/tree/ChangeLog?h=elfutils-0.166
gcc 5.4.0 6.1.0 https://gcc.gnu.org/gcc-6/changes.html
gdb 7.11 7.11.1 https://www.gnu.org/software/gdb/download/ANNOUNCEMENT
glibc 2.23 2.24 https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html
kmod 22 23 http://git.kernel.org/cgit/utils/kernel/kmod/kmod.git/tree/NEWS?id=a29268d00e335afb34d93d56898cac531d038867
libmnl 1.0.3 1.0.4 N/A
libpng 1.6.23 1.6.24 https://sourceforge.net/p/libpng/code/ci/libpng16/tree/CHANGES
libressl 2.3.5 2.4.2 https://github.com/libressl-portable/portable/blob/v2.4.2/ChangeLog
make 4.1 4.2.1 http://lists.gnu.org/archive/html/info-gnu/2016-05/msg00013.html, http://lists.gnu.org/archive/html/info-gnu/2016-06/msg00005.html
mysql 5.7.13 5.7.14 https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-14.html
qemu 2.5.1 2.6.0 http://wiki.qemu.org/ChangeLog/2.6
sqlite 3.12.2 3.14.1 https://www.sqlite.org/changes.html
systemd 230 231 https://github.com/systemd/systemd/blob/v231/NEWS

I wanted to include the following:

Package Old New Changelog
binutils 2.26 2.27 https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27
libgcrypt 1.6.5 1.7.2 https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000392.html

However with both gcc 6.1.0 and gcc 5.4.0:

  1. binutils 2.27 (commit) results in the following kernel panic on RPi2 (didn't bother booting Generic):

panic

binutils 2.26.1 does boot normally, so it's a problem introduced with 2.27. I saw little point in bumping to 2.26.1.

  1. libgcrypt 1.72 (commits: 1, 2, 3) fails to build on Generic:
libtool: link: /home/neil/projects/scratch/alternates/LibreELEC.tv/build.LibreELEC-Generic.x86_64-8.0-devel/toolchain/bin/x86_64-libreelec-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/libgcrypt_la-visibility.o .libs/libgcrypt_la-misc.o .libs/libgcrypt_la-global.o .libs/libgcrypt_la-sexp.o .libs/libgcrypt_la-hwfeatures.o .libs/libgcrypt_la-stdmem.o .libs/libgcrypt_la-secmem.o .libs/libgcrypt_la-missing-string.o .libs/libgcrypt_la-fips.o .libs/libgcrypt_la-hmac256.o .libs/libgcrypt_la-context.o .libs/hwf-x86.o  -Wl,--whole-archive ../cipher/.libs/libcipher.a ../random/.libs/librandom.a ../mpi/.libs/libmpi.a ../compat/.libs/libcompat.a -Wl,--no-whole-archive  -L/home/neil/projects/scratch/alternates/LibreELEC.tv/build.LibreELEC-Generic.x86_64-8.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib /home/neil/projects/scratch/alternates/LibreELEC.tv/build.LibreELEC-Generic.x86_64-8.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libgpg-error.a  -march=x86-64 -m64 -Os -flto -mmmx -msse -msse2 -mfpmath=sse -Wl,--version-script=/home/neil/projects/scratch/alternates/LibreELEC.tv/build.LibreELEC-Generic.x86_64-8.0-devel/libgcrypt-1.7.2/src/libgcrypt.vers -march=x86-64 -m64 -Wl,--as-needed -fuse-ld=gold -fuse-linker-plugin -flto   -Wl,-soname -Wl,libgcrypt.so.20 -o .libs/libgcrypt.so.20.1.2
/home/neil/projects/scratch/alternates/LibreELEC.tv/build.LibreELEC-Generic.x86_64-8.0-devel/toolchain/lib/gcc/x86_64-libreelec-linux-gnu/6.1.0/../../../../x86_64-libreelec-linux-gnu/bin/ld.gold: error: /tmp/ccVygTe1.ltrans16.ltrans.o: requires dynamic R_X86_64_PC32 reloc against '.Laes_consts' which may overflow at runtime; recompile with -fPIC
collect2: error: ld returned 1 exit status

The AES-NI SSE3 feature is added in 1.7.0.

So for now I've left out binutils and libgcrypt - suggestions welcome on how to fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment