unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: AVR toolchain and AVR libc
Date: Sun, 23 Feb 2020 22:46:11 +0000	[thread overview]
Message-ID: <ICMgXtkEsDGyp2DMw_8uvRBBSWMC8oFV-bW67vXEcM1EMC7zBDg_1iLupE8_Lv4NU_OWj_VyPWv3VMovL9Q7XgNQ6fX-Of9-4wKZ51P78_c=@elenq.tech> (raw)
In-Reply-To: <jbKMxDgVc7bLIIoYsJMX_Yhhh-H-zoCmOmtoMlW-cdJcDvqPx6Pv5OsGcUhMK9_zUvOuLJAF1_gLpbmMBjSw5zq5PYsLpMFKuh6PXkgdPxQ=@elenq.tech>

BTW, is there any resource point to why the package of the avr-toolchain 5.5 is broken?

I may spend some time trying to make it work.


ElenQ Technology
Ethical Innovation

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, February 23, 2020 6:54 PM, Ekaitz Zarraga <ekaitz@elenq.tech> wrote:

> > This is the compiler treating the strict prototype warning as an
>
> > error. You could get around this by using the ALLOW_WARNINGS=yes
> > makeflag supported by the Makefile of the QMK firmware project.
> > make <make-target> ALLOW_WARNINGS=yes
>
> It worked!
> Thanks a lot.

  reply	other threads:[~2020-02-23 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 13:53 AVR toolchain and AVR libc Ekaitz Zarraga
2020-02-23 14:28 ` Arun Isaac
2020-02-23 14:35   ` Ekaitz Zarraga
2020-02-23 17:50     ` Arun Isaac
2020-02-23 17:54       ` Ekaitz Zarraga
2020-02-23 22:46         ` Ekaitz Zarraga [this message]
2020-02-24  7:15           ` Arun Isaac
2020-02-28 15:52             ` Arun Isaac
2020-02-28 18:55               ` Ekaitz Zarraga
2020-02-29 10:37                 ` Arun Isaac

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ICMgXtkEsDGyp2DMw_8uvRBBSWMC8oFV-bW67vXEcM1EMC7zBDg_1iLupE8_Lv4NU_OWj_VyPWv3VMovL9Q7XgNQ6fX-Of9-4wKZ51P78_c=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=arunisaac@systemreboot.net \
    --cc=help-guix@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).