From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Tom Rini <trini@konsulko.com>
Cc: Leo Liang <ycliang@andestech.com>,
Alexandre Ghiti <alexandre.ghiti@canonical.com>,
Rick Chen <rick@andestech.com>,
Aurelien Jarno <aurelien@aurel32.net>,
u-boot@lists.denx.de, bmeng.cn@gmail.com, sjg@chromium.org
Subject: Re: [PATCH] riscv: Fix build against binutils 2.38
Date: Sun, 2 Oct 2022 03:52:00 +0200 [thread overview]
Message-ID: <ddd621ec-2b56-9855-2120-b1df612dd542@canonical.com> (raw)
In-Reply-To: <20221001235734.GB3044094@bill-the-cat>
On 10/2/22 01:57, Tom Rini wrote:
>>> Any thoughts or comments ?
>> In our Docker container command
>>
>> tools/buildman/buildman -o build -w -E -W -e --board qemu-riscv32_spl
>>
>> leads to build/toolchain with content
>>
>> gcc /opt/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux-gcc
>> path /opt/gcc-11.1.0-nolibc/riscv64-linux/bin
>> cross riscv64-linux-
>> arch riscv64
>>
>> When compiling qemu-riscv32_defconfig with Alexandre's patch and
>>
>> export
>> CROSS_COMPILE=/opt/gcc-11.1.0-nolibc/riscv64-linux/bin/riscv64-linux-
>>
>> I see undefined reference to `__ashldi3'.
> Another reason to port the generic *di3 option from modern Linux kernel.
Why should we use a 64bit toolchain for 32bit RISC-V when a 32bit
toolchain is available?
Fixing the Docker container and buildman seems to be the logical way
forward.
Cf.
https://source.denx.de/u-boot/custodians/u-boot-efi/-/commits/riscv
https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/13657
Best regards
Heinrich
next prev parent reply other threads:[~2022-10-02 1:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 13:47 [PATCH] riscv: Fix build against binutils 2.38 Alexandre Ghiti
2022-01-28 14:15 ` Bin Meng
2022-01-28 18:03 ` Heinrich Schuchardt
2022-01-28 18:19 ` Aurelien Jarno
2022-01-28 18:28 ` Aurelien Jarno
2022-01-28 18:22 ` Heinrich Schuchardt
2022-02-17 9:24 ` Leo Liang
2022-02-17 10:28 ` Alexandre Ghiti
2022-02-19 8:51 ` Leo Liang
2022-02-21 16:42 ` Alexandre Ghiti
2022-03-01 3:21 ` Leo Liang
2022-03-03 11:06 ` Leo Liang
2022-03-09 6:31 ` Leo Liang
2022-03-10 8:03 ` Alexandre Ghiti
2022-04-07 9:12 ` Leo Liang
2022-04-12 9:14 ` Alexandre Ghiti
2022-04-13 1:49 ` Leo Liang
2022-10-01 23:24 ` Heinrich Schuchardt
2022-10-01 23:57 ` Tom Rini
2022-10-02 1:52 ` Heinrich Schuchardt [this message]
2022-10-02 17:16 ` Tom Rini
2022-10-02 17:25 ` Tom Rini
2022-06-23 13:40 ` Heiko Stübner
2022-08-30 20:28 ` Christian Stewart
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=ddd621ec-2b56-9855-2120-b1df612dd542@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=alexandre.ghiti@canonical.com \
--cc=aurelien@aurel32.net \
--cc=bmeng.cn@gmail.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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.