[yocto] Quick confirmation about multilib

[Nicholas Tsirakis]

Sure, thanks for the reply. The image itself should is 64 bit and I want to
add an additional toolchain to my image that can run 32-bit binaries. I am
trying to build a 32-bit glibc that will be part of this toolchain.

Now, when I go to build, there is a new folder that got created in
tmp-glibc for the lib32-* files:

tmp-glibc/work/x86-oemllib32-linux/lib32-*

and upon entering the lib32-glibc folder, I'm seeing this:

tmp-glibc/work/x86-oemllib32-linux/lib32-glibc/2.25-r0/build-x86_64-oemllib32-linux/

I'm just not sure if that "x86_64" in the build folder name is correct. I
may be doing something entirely wrong as well; this is my first time using
multilib. As an FYI, I have the following to my local.conf:
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

Any clarification is appreciated.

On Wed, Dec 12, 2018 at 12:04 PM Burton, Ross <ross.burton at intel.com> wrote:

> On Wed, 12 Dec 2018 at 16:59, Nicholas Tsirakis <niko.tsirakis at gmail.com>
> wrote:
> > I'm trying to build a 32-bit toolchain for my 64-bit image using
> multilib and was hoping someone could confirm something for me. I am seeing
> issues when building lib32-glibc, and I can't tell if it's attempting to
> build properly. The resulting build files are created in a folder called
> "x86_64-oemllib32-..." - is this correct? Or should it be "x86-oemllib32"
> being that it's a 32-bit library?
>
> Can you clarify here was should be 32-bit and what should be 64-bit?
>
> Ross
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181212/28e80597/attachment.html>