From: Arun Isaac <arunisaac@systemreboot.net>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: help-guix@gnu.org
Subject: Re: AVR toolchain and AVR libc
Date: Sun, 23 Feb 2020 23:20:15 +0530 [thread overview]
Message-ID: <cu7h7zhqjl4.fsf@systemreboot.net> (raw)
In-Reply-To: <aP4JZwl3UAmiBWcEZIf_GAvFJ47n4By63HxlqMurrtIOJw3NLX7Iys8APV9pN4VhDSuSf6kHUcDcH4YRBXI5RsUMpXa9ihoKFrgO6eQTbYw=@elenq.tech>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
> Now I made this environment and it still fails.
>
> guix environment --ad-hoc unzip wget avr-toolchain@4.9 dfu-programmer dfu-util gcc-toolchain arm-none-eabi-toolchain
>
> Now the error is different:
> /gnu/store/p7cs7wfvz26jyyr1qifkl68cr9i61ndq-profile/avr/include/avr/power.h:1149:1: error: function declaration isn't a prototype [-Werror=strict-prototypes]
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
I tested this on the latest master (commit
b353028ea5e0ac7b69e7fed4f224c7cb07015ec9) of the QMK firmware git repo
with ergodox_ez:default as the make target, and it builds
successfully. If you tell me what make target you are using, I could
check with that also.
> As I'm using Guix as a package manager I was able to try to compile
> everything from my distro's package manager's tools and it worked...
> I don't know what's going on on Guix.
Maybe, the avr-gcc or avr-libc version is different in Guix and your
other distro's package manager. That could be a reason for the
strict-prototype warning being triggered in one case but not in the
other.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-23 17:50 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 [this message]
2020-02-23 17:54 ` Ekaitz Zarraga
2020-02-23 22:46 ` Ekaitz Zarraga
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=cu7h7zhqjl4.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=ekaitz@elenq.tech \
--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).