[PATCH 1/3] Dockerfile: Install riscv32 toolchain from kernel.org

Tom Rini trini at konsulko.com
Tue Mar 31 17:15:53 CEST 2020


On Sat, Mar 28, 2020 at 07:55:37AM +0800, Bin Meng wrote:
> Hi Tom,
> 
> On Fri, Mar 27, 2020 at 11:25 PM Tom Rini <trini at konsulko.com> wrote:
> >
> > On Fri, Mar 27, 2020 at 02:05:55PM +0800, Bin Meng wrote:
> > > Hi Tom,
> > >
> > > On Fri, Mar 27, 2020 at 10:00 AM Tom Rini <trini at konsulko.com> wrote:
> > > >
> > > > On Fri, Mar 27, 2020 at 09:57:47AM +0800, Bin Meng wrote:
> > > > > Hi Tom,
> > > > >
> > > > > On Fri, Mar 27, 2020 at 12:14 AM Tom Rini <trini at konsulko.com> wrote:
> > > > > >
> > > > > > On Thu, Mar 26, 2020 at 09:04:52AM -0700, Bin Meng wrote:
> > > > > >
> > > > > > > This is required to build GRUB UEFI target for RISC-V 32-bit.
> > > > > > >
> > > > > > > Signed-off-by: Bin Meng <bmeng.cn at gmail.com>
> > > > > >
> > > > > > Since we can use the 64bit toolchain for 32bit U-Boot, can we not pass
> > > > > > GRUB the right flags to use the same toolchain?  Thanks!
> > > > >
> > > > > The 32-bit GRUB won't build with the 64-bit toolchain as of the
> > > > > grub-2.04 branch we are using.
> > > >
> > > > Is that something that upstream has fixed or will fix / can be fixed and
> > > > we can bump the tag we're using for?
> > >
> > > I tried the latest upstream GRUB, and it still cannot be built using
> > > riscv64 toolchain from kernel.org.
> >
> > Can that be fixed?  Would that be accepted?  Thanks!
> >
> 
> I reported this issue to the grub mailing list. For now I believe we
> should stick to current 2.04 until upstream has a solution for it.

Has upstream said anything here?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200331/41252a06/attachment.sig>


More information about the U-Boot mailing list