On 05/07/2013 01:35 PM, Mark Hatle wrote:
>>> - nativesdk -- runs on the 'sdkhost' (variant called 'crosssdk')
>>
>> Is this related to the SDKMACHINE setting?
>>
>
> Yes that's the variable I was thinking of. You can build an SDK for
> 'i586' on your x86_64 host for instance.
>
So in my case, si
On 05/07/2013 11:36 AM, Mark Hatle wrote:
> On 5/7/13 11:09 AM, Kyle Farnsworth wrote:
>> I'm a bit confused about what exactly meta-toolchain is building? It
>> seems to be bitbaking gcc and creating a toolchain with the prefix
>> x86_64-oesdk-linux- (default SDK_PREFIX
I'm a bit confused about what exactly meta-toolchain is building? It
seems to be bitbaking gcc and creating a toolchain with the prefix
x86_64-oesdk-linux- (default SDK_PREFIX) but I'm not sure what it is.
Is it a cross-compile for my target MACHINE or a compiler for my build
machine? Based on
Signed-off-by: Kyle Farnsworth
---
meta/classes/insane.bbclass |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index f52fcea..e1827be 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
tinylogin installs the executable using the mode setting "-m 4755" which
sets the userID bit (-rwsr-xr-x). From what I read that seems like the
right thing to do. But when it gets added to the rootfs image it ends
up with a group and user id = 1000. Then when getty attempts to login I
get this m
