You don't need a full download. In the past I've used binary diffs with great success. So if the update size is your biggest concern, the tradeoff of computing and applying the binary diff might be wo

Thanks a lot for your suggestion! But doesn't this line imply that recipes which don't supply systemd servies files won't work since the init.d scipt fallback will be disabled?

My thud based system installs openssh-sshd but I want to have sshd disabled by default. So I checked the docs how to disabled a systemd service by default and found SYSTEMD_AUTO_ENABLE, perfect. After

Bruce, <richard.weinberger@...> wrote: I think I found the source if my confusion, the i686-poky-linux compiler *is* a biarch gcc but defaults to -m32. When I pass -m64 to it, it actually genera

Bruce, <bruce.ashfield@...> wrote: If I understand the problem correctly, the root of the problem is that yocto "degrades" to i686. When I set DEFAULTTUNE to i586 for a 64bit machine I'd exp

Bruce, <bruce.ashfield@...> wrote: This was my plan, but yocto always create a 32bit toolchain when it set DEFAULTTUNE to i586 for a 64bit machine. Yes, it builds with i686-poky-linux. :-(

[Resending with correct mail] Richard, This was my hope, and this is also what I get when doing such builds manually. Having a x86_64 gcc and building userspace with "-m32" appended. Yocto seems to tr

<richard.purdie@...> wrote: I went this approach for now. That way I get i586 userland and an SDK with both 32bit and 64bit toolchains. The SDK offers me multiple environment files to

<richard.weinberger@...> wrote: *kind ping*

Richard, <richard.purdie@...> wrote: My idea was having a 32bit only SDK. In my case I really don't need 64bit userspace. On the other hand, having both 32bit and 64bit libs in the SDK

Hi! I have a hard time understanding how to build a distro with x86_64 kernel, i586 userland and an SDK for that. In the beginning I assumed and have been told on IRC that multilib is the way to go. B