Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/6] package/riscv64-elf-toolchain: new package
Date: Mon, 03 May 2021 09:09:01 +0200	[thread overview]
Message-ID: <87o8ds2t0y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210503085733.59777dce@windsurf> (Thomas Petazzoni's message of "Mon, 3 May 2021 08:57:33 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello,
 > On Mon, 03 May 2021 08:17:33 +0200
 > Peter Korsgaard <peter@korsgaard.com> wrote:

 >> Out of interest, why is that? For the ARM32 case it was a question of
 >> 32bit / 64bit, but that does not seem to be the issue here?
 >> 
 >> Just crappy firmware or are there any deeper differences between a bare
 >> metal and Linux toolchain on riscv64?

 > It is not yet 100% sure what's going on. The firmware clearly doesn't
 > build with a Linux toolchain. I've done a bit of work to try to get it
 > to build, by adding -ffrestanding -nostdinc, but it does include a few
 > standard headers (stdint.h for example). Once this was fixed, the build
 > system of the firmware uses a specific gcc spec file, called nano.spec,
 > which isn't available except in their bare-metal toolchain.

 > So for now, I opened a bug report at
 > https://github.com/starfive-tech/beagle_ddrlnit/issues/4, and decided
 > to go on with building this with the recommended bare-metal toolchain.

Ok, thanks for the description.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2021-05-03  7:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 21:21 [Buildroot] [PATCH v2 0/6] Support for the BeagleV platform Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 1/6] boot/opensbi: add options to enable/disable image installation Thomas Petazzoni
2021-05-03  0:08   ` Alistair Francis
2021-05-03 11:26   ` Bin Meng
2021-05-02 21:21 ` [Buildroot] [PATCH v2 2/6] configs/beaglev_defconfig: new defconfig Thomas Petazzoni
2021-05-03  0:12   ` Alistair Francis
2021-05-03  1:14   ` Alistair Francis
2021-05-02 21:21 ` [Buildroot] [PATCH v2 3/6] package/riscv64-elf-toolchain: new package Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 4/6] boot/beaglev-ddrinit: " Thomas Petazzoni
2021-05-03 11:30   ` Bin Meng
2021-05-03 11:53     ` Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 5/6] boot/beaglev-secondboot: " Thomas Petazzoni
2021-05-03 11:31   ` Bin Meng
2021-05-02 21:21 ` [Buildroot] [PATCH v2 6/6] configs/beaglev: enable building of low-level firmware Thomas Petazzoni
2021-05-03 11:33   ` Bin Meng
2021-05-02 21:21 ` [Buildroot] [PATCH v2 0/6] Support for the BeagleV platform Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 1/6] boot/opensbi: add options to enable/disable image installation Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 2/6] configs/beaglev_defconfig: new defconfig Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 3/6] package/riscv64-elf-toolchain: new package Thomas Petazzoni
2021-05-03  0:14   ` Alistair Francis
2021-05-03  6:54     ` Thomas Petazzoni
2021-05-03  7:11       ` Alistair Francis
2021-05-03  7:13         ` Thomas Petazzoni
2021-05-03  7:29           ` Alistair Francis
2021-05-03  6:17   ` Peter Korsgaard
2021-05-03  6:57     ` Thomas Petazzoni
2021-05-03  7:09       ` Peter Korsgaard [this message]
2021-05-02 21:21 ` [Buildroot] [PATCH v2 4/6] boot/beaglev-ddrinit: " Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 5/6] boot/beaglev-secondboot: " Thomas Petazzoni
2021-05-02 21:21 ` [Buildroot] [PATCH v2 6/6] configs/beaglev: enable building of low-level firmware Thomas Petazzoni
2021-05-03  7:18   ` Drew Fustini
2021-05-03  7:32     ` Thomas Petazzoni

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=87o8ds2t0y.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox