Hi Alex,

On Thu, Nov 15, 2018 at 6:02 PM Alexander Graf <ag...@suse.de> wrote:
>
>
>
> On 15.11.18 02:48, Bin Meng wrote:
> > Hi Alex,
> >
> > On Thu, Nov 15, 2018 at 1:02 AM Alexander Graf <ag...@suse.de> wrote:
> >>
> >> On 11/14/2018 04:34 PM, Bin Meng wrote:
> >>> On Wed, Nov 14, 2018 at 11:28 PM Andreas Schwab <sch...@suse.de> wrote:
> >>>> On Nov 14 2018, Bin Meng <bmeng...@gmail.com> wrote:
> >>>>
> >>>>> - use riscv32-* toolchain to build riscv64 target (-m64 required)
> >>>>> - use riscv64-* toolchain to build riscv32 target (-m32 required)
> >>>> riscv does not use -m64/-m32.
> >>>>
> >>> Ah, yes! I was brain-dead. I actually wanted to say
> >>>
> >>> - use riscv32-* toolchain to build riscv64 target (riscv32 cpu detected)
> >>> - use riscv64-* toolchain to build riscv32 target (riscv64 cpu detected)
> >>>
> >>> and before I hit 'send', I changed it to -m32/-m64. Sorry for the wrong 
> >>> message.
> >>
> >> So what would you expect instead?
> >>
> >
> > I was expecting using the riscv32-* toolchain we can still build grub
> > for riscv64 (or using riscv64-* toolchain to build riscv32), i.e. the
> > similar way to what current U-Boot build for targets like x86, riscv.
>
> Can you please post a patch on top of my series for that? I'm not sure
> how that would work :).

I have looked at the autoconf, and it seems that such configuration
cannot be done without adding a new configure option for grub to
override the $target_cpu which was automatically guessed from the
toolchain triples by autoconf.

Guess we have to leave such "limitation" :)

Regards,
Bin

_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to