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
Op 19 mrt. 2012, om 21:44 heeft Norman Schleicher het volgende geschreven:
Hello,
I followed the WIKI information howto build angstrom. After updating, all
packages are build again.
How can I avoid that ?
It's due to this:
OE Build Configuration:
BB_VERSION= 1.15.1
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = beaglebone
DISTRO= angstrom
DISTRO_VERSION= v2012.03-core
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
meta-angstrom =
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
2012/3/8 Gary Thomas g...@mlbassoc.com
On 2012-03-08 12:20, Ulf Samuelsson wrote:
You can at time rlogin even if you do not get a prompt.
also, NFS mounting will give you access to logs onthe NFS host.
I can't log in - no services get started because the postinst functions
have not run