From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Toolchain bugs how to correct them
Date: Fri, 28 Sep 2018 00:06:09 +0300 [thread overview]
Message-ID: <8736tu4pmm.fsf@tkos.co.il> (raw)
In-Reply-To: <11cbd73b-101a-5d22-70a6-a3dcf4f69b54@micronovasrl.com>
Hi Giulio,
Giulio Benetti writes:
> Hello everybody,
>
> if an external toolchain has a bug, i.e. "toolchain-external-synopsys-arc"
> and need a patch I've found, how does it work?
> Can someone point me somewhere to understand?
You should contact the Buildroot ARC support maintainers. See the "ARC
Maintainers" entry in DEVELOPERS. In addition, the git log indicates
that Evgeniy Didin has been sending ARC toolchain version bumps.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-09-27 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 20:45 [Buildroot] Toolchain bugs how to correct them Giulio Benetti
2018-09-27 21:06 ` Baruch Siach [this message]
2018-09-29 22:16 ` Giulio Benetti
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=8736tu4pmm.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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