This time it created
angstrom-eglibc-i686-armv7a-v2012.03-core-toolchain.tar.bz2 as expected.
Weird indeed!
On 03/20/2012 05:54 AM, Koen Kooi wrote:
Op 20 mrt. 2012, om 05:09 heeft Kyle Guilbert het volgende geschreven:
I'd like to build a newer SDK for the beaglebone. When I bitbake meta-toolchain
(with MACHINE=beaglebone of course), I get the following sdk:
angstrom-eglibc-i686-armv5te-v2012.03-core-toolchain.tar.bz2
The default CFLAGS used by the generated cross-gcc is "-march=armv5te -marm
-mthumb-interwork -mtune=arm926ej-s" and so on. Is this the right way to create the
appropriate SDK for my target? I was expecting -march=armv7-a, -mtune=cortex-a8, etc.
That is really weird, I get
angstrom-eglibc-x86_64-armv7a-v2012.03-core-toolchain.tar.bz2. Can you please
post the buildinfo banner that appears at the start of the build?
regards,
Koen
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
