Hi all.

I've incorrectly reported a build failure in the support system.
<https://support.linaro.org/hc/en-us/requests/1876>
-But I'm posting a copy to this list, in order to follow Victor's advice.

I've suggested a couple of changes, which makes ABE a little more compatible.
Though I can still not build the toolchain on my PowerBook G4, I think that my 
two modifications might ease building on Intel based Macs and perhaps other 
architectures in addition.

In short:
* Use getconf instead of /proc/cpuinfo (you're already using getconf in 
configure.ac).
* By default use twice as many cores for -jN as usual. (If you have 2 cores, 
use -j4)
* Change the architecture from 'Power Macintosh' (which contains an offending 
space) to 'powerpc'.

...And here's "configure.ac.patch":

---8<-----8<-----8<-----
diff --git a/configure.ac b/configure.ac
index 1bf3593..8cc4986 100644
--- a/configure.ac
+++ b/configure.ac
@@ -49,9 +49,10 @@ AC_SUBST(DBPASSWD)
 DBHOST=${dbhost}
 AC_SUBST(DBHOST)
 
-CPUS="`grep -c proces /proc/cpuinfo`"
+
+let CPUS=2*`getconf _NPROCESSORS_ONLN`
 AC_SUBST(CPUS)
-CORES="`grep cores /proc/cpuinfo | tail -1 | cut -d ' ' -f 3`"
+#CORES="`grep cores /proc/cpuinfo | tail -1 | cut -d ' ' -f 3`"
 AC_SUBST(CORES)
 LIBC="`getconf GNU_LIBC_VERSION`"
 AC_SUBST(LIBC)
@@ -59,6 +60,7 @@ KERNEL="`uname -r`"
 AC_SUBST(KERNEL)
 BUILDHOST="`${srcdir}/config.guess`"
 BUILD_ARCH="`uname -m`"
+[[ "`uname -s`" == "Darwin" ]] && BUILD_ARCH="`uname -p`"
 AC_SUBST(BUILD_ARCH)
 AC_SUBST(BUILDHOST)
 HOSTNAME="`uname -n`"
--->8----->8----->8-----

Apart from that, I'd like to report a successful build on Cubieboard2 running 
Armbian.
I built for the aarch64 architecture, and I'm currently attempting to build 
Armbian for beelink GT1 using the new shiny Linaro toolchain. :)
...and what a pleasure, there's no fan-noise when building on the Cubieboard2!


Love
Jens

_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Reply via email to