public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Vijay Holimath <vijay.holimath@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Applying patches for RISC-V in crosstool-ng
Date: Mon, 15 Jun 2020 15:46:34 +0100	[thread overview]
Message-ID: <CAH6eHdSZwET+zgvnXSEQHC3k8F8ABVLUMMqsVM9vh2HYcK9+Ow@mail.gmail.com> (raw)
In-Reply-To: <CAL7Ob90fRYskmjeqAHP3K_naeL_R3mOEvR2055wStbHf2Duwxg@mail.gmail.com>

On Mon, 15 Jun 2020 at 15:17, Vijay Holimath <vijay.holimath@gmail.com> wrote:
>
> I know in general how to apply patch. But the patch I need to apply is for RISC-V makefile; in crosstool-ng there seem to be no Makefile for RISC-V.

OK. That's still nothing to do with GCC. The repository you linked to
is not GCC code. Crosstool-ng is also not GCC code. Maybe you should
ask on a crosstool-ng list, or ask the author of that change.


> I think in crosstool-ng you can configure RISC-V options using 'ct-ng menuconfig' once you configured then one need to use ct-ng build to to build compiler.  The crosstool-ng will build compiler using the config options, I think there is no Makefile as such for RISC-V. However, I might be wrong.
>
> On Mon, Jun 15, 2020 at 7:33 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>>
>> On Mon, 15 Jun 2020 at 15:00, Vijay Holimath via Gcc-help
>> <gcc-help@gcc.gnu.org> wrote:
>> >
>> > Hello All,
>> >
>> > I need to apply this patch:
>> > https://github.com/bespoke-silicon-group/bsg_manycore/blob/master/software/riscv-tools/newlib.patch
>> > for
>> > RISC-V and build compiler using crosstool-ng. Can you please tell me how to
>> > do it?
>>
>> That has nothing to do with GCC. Try searching the web for "how to
>> apply a patch".

  reply	other threads:[~2020-06-15 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 13:58 Vijay Holimath
2020-06-15 14:03 ` Jonathan Wakely
2020-06-15 14:17   ` Vijay Holimath
2020-06-15 14:46     ` Jonathan Wakely [this message]
2020-06-15 22:01 ` Jim Wilson
2020-06-16 12:07   ` Vijay Holimath

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=CAH6eHdSZwET+zgvnXSEQHC3k8F8ABVLUMMqsVM9vh2HYcK9+Ow@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=vijay.holimath@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).