From: Vijay Holimath <vijay.holimath@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: RISC-V G++ and Gfortran Help
Date: Mon, 9 Mar 2020 21:03:07 +0530 [thread overview]
Message-ID: <CAL7Ob93Q10-9QzNJ9gLEW9CUT4HgWz-f3vnfaFDzTroxWYjcaw@mail.gmail.com> (raw)
In-Reply-To: <CAL7Ob93oqVKeu9SqjF-shn61DFE+5eJrkOEzmupuVt99x-V14w@mail.gmail.com>
Moreover, in cross-ng tool (https://crosstool-ng.github.io/) in ct-ng
menu-config there are no option to build C++ and gfortran for RISC-V
architecture. This thing is, I need to modify certain source codes in the
source tree and rebuild both C++ and gfortran for RISC-V architecture. So,
I am looking for a command or tool or config file which will allow me
download all source files for C++ and gfortran compilers, modify certain
part of source code in source tree and re build the compiler from scratch.
I request your assistance in this regard.
Many Thanks.
On Mon, Mar 9, 2020 at 7:27 PM Vijay Holimath <vijay.holimath@gmail.com>
wrote:
> Dear Sir,
>
> I would like to build RISC-V g++ and gfortran compiler by downloading all
> source codes to host pc (for linux OS) and then rebuild compiler from
> scratch. I can build RISC-V gcc compiler from scratch by downloading to
> host pc using https://crosstool-ng.github.io/ However, I have not
> found any such cross compiler tool for g++ and gfortran. May I request you
> to guide me on how to build RISC-V cross C ++ and gfortran compiler from
> source codes?
>
> I look forward to hearing from you soon.
>
> Thanking you.
>
> Sincerely,
> -Vijay
>
>
next prev parent reply other threads:[~2020-03-09 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 13:57 Vijay Holimath
2020-03-09 14:30 ` Jonathan Wakely
2020-03-09 15:33 ` Vijay Holimath [this message]
2020-03-09 16:36 ` Jonathan Wakely
2020-03-09 22:02 ` Jim Wilson
2020-03-10 2:00 ` Vijay Holimath
2020-03-11 23:24 ` Jim Wilson
2020-03-12 0:53 ` Vijay Holimath
2020-06-15 4:04 ` Vijay Holimath
2020-06-15 21:49 ` Jim Wilson
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=CAL7Ob93Q10-9QzNJ9gLEW9CUT4HgWz-f3vnfaFDzTroxWYjcaw@mail.gmail.com \
--to=vijay.holimath@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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).