From: Vijay Holimath <vijay.holimath@gmail.com>
To: Jim Wilson <jimw@sifive.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: RISC-V G++ and Gfortran Help
Date: Thu, 12 Mar 2020 06:23:07 +0530 [thread overview]
Message-ID: <CAL7Ob92Nx0iT8JXc9bP6TtEHdaSg0mqr2JQnQw3KgsT2xGeXVg@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaY3HeUsmfHPQGtjA2zMFWaT583dNWiQ0514NRwOQ5Wn2Q@mail.gmail.com>
Never mind, I have generated config files for C++ and fortran. Thanks for
your time Jim.
On Thu, Mar 12, 2020 at 4:55 AM Jim Wilson <jimw@sifive.com> wrote:
> On Mon, Mar 9, 2020 at 7:00 PM Vijay Holimath <vijay.holimath@gmail.com>
> wrote:
> > Thanks Jim. Yes, I can see C++ and Fortran for new version of
> crosstool-ng. However, I am unable to generate .config file using the
> following instructions:
> >
> > Enable newlib build (C-library section)
> > Enable "Build a multilib toolchain" (Target options section)
> > and also
> > selected C++ (C compiler section)
> > as mentioned in
>
> What exact problem do you run into?
>
> > I have attached my version of .config file which I build gcc from
> scratch. May I request you to edit this file send me two .config files? One
> for C++ and other fortran.
>
> I respectfully decline. I don't have such .config files and have no
> interest in generating them.
>
> If you can't figure out how to use crosstool-ng, you could try using
> github.com/riscv/riscv-gnu-toolchain instead. Or maybe download a
> prebuilt toolchain which is available from various sources like
> sifive.com/boards.
>
> Jim
>
next prev parent reply other threads:[~2020-03-12 0:53 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
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 [this message]
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=CAL7Ob92Nx0iT8JXc9bP6TtEHdaSg0mqr2JQnQw3KgsT2xGeXVg@mail.gmail.com \
--to=vijay.holimath@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jimw@sifive.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).