From: Denys Dmytriyenko <denis@denix.org>
To: d.sabato@4sigma.it
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] aarch64 external-toolchain multilib support
Date: Tue, 27 Feb 2024 16:02:39 -0500 [thread overview]
Message-ID: <20240227210239.GD6072@denix.org> (raw)
In-Reply-To: <llGR.1709056307395060423.8aZp@lists.yoctoproject.org>
Unlike x86, there are separate compilers for 64bit Arm and 32bit Arm. The
external toolchain you use is aarch64-none-linux-gnu and is for 64bit, while
32bit toolchain is called arm-none-linux-gnueabihf. TCMODE=external-arm does
not support dual toolchains at the same time, hence no multilib.
On Tue, Feb 27, 2024 at 09:51:47AM -0800, d.sabato via lists.yoctoproject.org wrote:
> Hello,
> I use pre-built external ARM toolchain to build iMx8 distro 64 bit.
>
> TCMODE = "external-arm"
> EXTERNAL_TOOLCHAIN = "/opt/arm-gnu-toolchain-13.2.Rel1-x86_64-aarch64-none-linux-gnu"
>
> I'd like to generate 32bit version of libraries for my sysroot so I add following in my build/local.conf :
>
> require conf/multilib.conf
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE:virtclass-multilib-lib32 = "armv7athf-neon"
> IMAGE_INSTALL:append := " lib32-glibc lib32-libgcc lib32-libstdc++"
>
> Am I doing right ?
>
> Build Configuration:
> BB_VERSION = "2.4.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "debian-12"
> TARGET_SYS = "aarch64-oe-linux"
> TUNE_FEATURES = "aarch64 armv8a crc cortexa53 crypto"
> TARGET_FPU = ""
> meta = "master:3c35416a8bff3a857004beadbd053d50eca30ce2"
> meta-oe
> meta-networking
> meta-python
> meta-filesystems = "master:39968837196cb48209b71e8852dd04a2f8ccdca8"
> meta-freescale = "master:7f0a7f3d19f564da0faf20e279b1b18a7f0068b6"
> meta-arm-toolchain
> meta-arm = "master:9bcc166bd5bb717aa86bb0464621a36abc51fa19"
>
> Thank you,
> Danilo
prev parent reply other threads:[~2024-02-27 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 17:51 aarch64 external-toolchain multilib support d.sabato
2024-02-27 21:02 ` Denys Dmytriyenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240227210239.GD6072@denix.org \
--to=denis@denix.org \
--cc=d.sabato@4sigma.it \
--cc=meta-arm@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).