From: Denys Dmytriyenko <denis@denix.org>
To: daniel.lehne@amk-drives.bg
Cc: meta-arago@arago-project.org
Subject: Re: Patch external-arm-toolchain on meta-arago-extras fails with gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf
Date: Wed, 6 Oct 2021 19:16:19 -0400 [thread overview]
Message-ID: <20211006231619.GM1528@denix.org> (raw)
In-Reply-To: <009401d7b447$0e119530$2a34bf90$@amk-drives.bg>
On Tue, Sep 28, 2021 at 11:58:48AM +0300, daniel.lehne@amk-drives.bg wrote:
> Hello,
>
> first, thanks for your great support on meta-arago layer and further
> enthusiastic developing.
>
> I'm trying to build a project with an external toolchain but failing on the
> recipe
> /meta-arm/meta-arm-toolchain/recipes-devtools/external-arm-toolchain/externa
> l-arm-toolchain.bb:do_install. I'm building in a docker container, with
> reduced layers using the ./oe-layertool-setup.sh command with following test
> config file. I've tried first
> gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf but it fails also, so I
> downgraded to gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf without
> success.
Hi, Daniel,
In order to post to the list you need to subscribe first. Otherwise your
messages are held in moderation queue along with other spam posts and have
very low chance to be seen.
It appears your layer configuration is not exactly correct. Arago Project uses
oe-layersetup tool along with config files to setup layers:
http://arago-project.org/git/projects/?p=oe-layersetup.git;a=summary
If you need to use prebuilt Arm external toolchain with meta-arago/dunfell,
then you should use 9.2-2019.12 version, according to this table:
http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment#Available_Layer_Configurations
Also, you need to pin meta-arm/meta-arm-toolchain layer to commit
c4f04f3fb66f8f4365b08b553af8206372e90a63, per the layer config:
http://arago-project.org/git/projects/?p=oe-layersetup.git;a=blob;f=configs/arago-dunfell-config.txt;hb=HEAD
That is due to some later changes in meta-arm-toolchain backported from master
that broke meta-arago. This hasn't been resolved yet.
Alternatively, instead of using prebuilt Arm toolchain, you can build and use
the internal toolchain, by setting or passing TOOLCHAIN_TYPE="internal"
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
prev parent reply other threads:[~2021-10-06 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 8:58 Patch external-arm-toolchain on meta-arago-extras fails with gcc-arm-9.2-2019.12-x86_64-arm-none-linux-gnueabihf daniel.lehne
2021-10-06 23:16 ` 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=20211006231619.GM1528@denix.org \
--to=denis@denix.org \
--cc=daniel.lehne@amk-drives.bg \
--cc=meta-arago@arago-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.