public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sagar Acharya <sagaracharya@tutanota.com>
To: David Brown <david@westcontrol.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, Gcc Help <gcc-help@gcc.gnu.org>
Subject: Re: Cross compiler riscv64 building
Date: Mon, 13 Feb 2023 13:02:37 +0100 (CET)	[thread overview]
Message-ID: <NO9dwoC--3-9@tutanota.com> (raw)
In-Reply-To: <176ec63a-41f5-768d-7864-239cd912ffb6@westcontrol.com>

Where can I get pre-built binaries for RPI3(aarch64) to compile for target riscv64?
Thanking you
Sagar Acharya
https://designman.org



9 Feb 2023, 18:58 by david@westcontrol.com:

> On 09/02/2023 12:20, Sagar Acharya via Gcc-help wrote:
>
>> I built binutils. Installed it at /usr/local/riscv64-unknown-elf directory
>>
>> Now, I tried building gcc with
>> ./configure --host=riscv64-unknown-elf
>> make
>>
>> However, the gcc directory within gcc-12.2.0 has no Makefile made during configure command. So it enters gcc-12.2.0/gcc dir, sees no Makefile prepared, exits with error.
>>
>> How do I solve this?
>>
>
> You are mixing up "host" and "target".  "Host" is the computer that runs the compiler, "target" is the computer that runs the compiled code.  So "host" for you will be an ARM system since you are doing your builds on an ARM computer, while "target" will be RISCV.
>
> If you really want to make your own cross-toolchain, you are going to have to spend a good amount of time reading about it and trying things out.  It is an educational process, but it takes work.  You can't expect to do it based on asking a few questions on a mailing list, any more than you can expect to learn C programming by asking questions in a C newsgroup.
>
> Again - I strongly suggest you use pre-built packages.  Even if you later decide that a DIY toolchain will be fun, having the pre-built packages for comparison will make things much easier.
>
> mvh.,
>
> David
>
>
>
>> Thanking you
>> Sagar Acharya
>> https://designman.org
>>
>>
>>
>> 8 Feb 2023, 16:48 by jwakely.gcc@gmail.com:
>>
>>> On Wed, 8 Feb 2023 at 11:12, Sagar Acharya via Gcc-help
>>> <gcc-help@gcc.gnu.org> wrote:
>>>
>>>>
>>>> How do I configure and build a cross compiler for target riscv64 of latest gcc on aarch64 musl based void linux.
>>>>
>>>> I have it's default gcc installed which I want to use for compiling.
>>>>
>>>
>>> See https://wiki.osdev.org/GCC_Cross-Compiler
>>>
>>> In summary:
>>> Download the gcc and binutils source.
>>> Configure binutils with --prefix=$DIR --target=riscv64-unknown-elf for
>>> some $DIR.
>>> Run make && make install.
>>> Configure gcc with the same --prefix and --target options.
>>> Run make && make install.
>>>
>>> If you want a hosted target like riscv64-unknown-linux-gnu for
>>> compiling user-space programs, then you'll need to have a copy of the
>>> target headers and libraries available, and point GCC to them with the
>>> --sysroot option.
>>> See https://wiki.osdev.org/Hosted_GCC_Cross-Compiler
>>>

  reply	other threads:[~2023-02-13 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 11:11 Sagar Acharya
2023-02-08 11:18 ` Jonathan Wakely
2023-02-09 11:20   ` Sagar Acharya
2023-02-09 13:28     ` David Brown
2023-02-13 12:02       ` Sagar Acharya [this message]
2023-02-13 12:42         ` David Brown
2023-02-09 14:31     ` Jonathan Wakely
2023-02-08 12:45 ` David Brown

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=NO9dwoC--3-9@tutanota.com \
    --to=sagaracharya@tutanota.com \
    --cc=david@westcontrol.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).