Bug fix release.
See script here to download, build, and optionally install it:
Code: Select all
(gdb) show configuration This GDB was configured as follows: configure --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf --with-auto-load-dir=$debugdir:$datadir/auto-load --with-auto-load-safe-path=$debugdir:$datadir/auto-load --with-expat --with-gdb-datadir=/usr/share/gdb (relocatable) --with-jit-reader-dir=/usr/lib/gdb (relocatable) --without-libunwind-ia64 --with-lzma --with-python=/usr (relocatable) --without-guile --with-separate-debug-dir=/usr/lib/debug (relocatable) --with-system-gdbinit=/etc/gdb/gdbinit --with-babeltrace ("Relocatable" means the directory can be moved with the GDB installation tree, and GDB will still find it.) (gdb)
I'm not sure - they were needed some time ago, but maybe now that native works properly ...
It takes around 50 hours to compile GCC on a Pi Zero which is why I cross compile it on a Pi3B+ (around 4.5 hours).
I tried doing the configure with only 2 options, languages (c,c++) and prefix(/usr/local/...) but the compile fails after about an hour (on the 3B+). I don’t remember the error exactly, but clearly some more stuff needs to be spcified.lianergoist wrote: ↑Sat Jul 28, 2018 8:48 amAlso +1 from me!
Maybe this is a stupid question, but why do we need the extra options to configure? Isn't it supposed to auto-detect that? Sure, things like --enable-languages=c,c++ makes sense, but the rest of it looks like it could/would/should be auto-detected.
Correct. Thanks for suggesting, I've updated readme. But be sure to check out that 6.3.0 binary is for cross-compiler only (not native) which means it is for Linux x64 machine(As Raspberrypi GCC Cross-Compiler) not for installing in raspberry pi. That's why I've highlighted the Binaries Description in the repo. which points out the use of each binary. Hope this will help.Perhaps the examples for wget etc should have 8.2 in rather than 6.3 so people can just cut and paste them?