All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12521] RISCV RV32IA selected, RV64GC output
Date: Wed, 04 Mar 2020 14:10:14 +0000	[thread overview]
Message-ID: <bug-12521-163-9dqIQyR3cP@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12521-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12521

--- Comment #4 from Mark Corbin <mark@dibsco.co.uk> ---
Hello

The configuration that you posted won't build due to a missing entry for the
location of your kernel configuration file (BR2_LINUX_KERNEL_DEFCONFIG).

The default RISC-V configuration for the 5.0.13 kernel is for a 64-bit build,
so you would need to provide an appropriate kernel config fragment to change
this to 32-bit. Note that there is now an 'rv32_defconfig' in the kernel tree
(since the 5.1 release).

However, the minimum ISA requirement for the 5.0.13 kernel is RV32im and later
kernels require RV32ima (see arch/riscv/Makefile), so it seems that you
wouldn't actually be able to build an RV32ia (or RV32i) kernel anyway.

Regards

Mark

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-03-04 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  0:18 [Buildroot] [Bug 12521] New: RISCV RV32IA selected, RV64GC output bugzilla at busybox.net
2020-02-03  9:35 ` [Buildroot] [Bug 12521] " bugzilla at busybox.net
2020-02-28 15:58 ` bugzilla at busybox.net
2020-02-28 16:33 ` bugzilla at busybox.net
2020-03-04 14:10 ` bugzilla at busybox.net [this message]
2020-05-18  7:37 ` bugzilla at busybox.net

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=bug-12521-163-9dqIQyR3cP@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.