> BTW, is there any resource point to why the package of the
> avr-toolchain 5.5 is broken?
I searched through my mail and I don't remember exactly where I read
that avr-toolchain 5.5 is broken and avr-toolchain 4.9 works. I was only
able to find this very old thread hinting about the problem.
h
Jorge writes:
> Hi. On a previous thread [1] I asked about best practices for Guix
> environment variables on foreign distro. My problem was not
> fundamentally solved, and it resurfaced again recently.
Hello, I'd say it's not a solved problem in general.
> In summary:
>
> I use Guix on an up
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 wrote:
> > This is the compiler trea
Hi. On a previous thread [1] I asked about best practices for Guix
environment variables on foreign distro. My problem was not
fundamentally solved, and it resurfaced again recently. In summary:
I use Guix on an updated Debian buster (with 59 packages from
buster-backports) to get some up-to-da
Julien Lepiller writes:
> Le 22 février 2020 07:09:46 GMT-05:00, Raghav Gururajan
> a écrit :
>>Hi Julien!
>>
>
> Unless I'm mistaken, I've pushed a patch to add auth-user-pass which
> is what you need. If that's not it, can you share the target
> configuration?
>
Here's an example configurati
> 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 ALLOW_WARNINGS=yes
>
It worked!
Thanks a lot.
> 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:
> err
Hello,
On Thu, Feb 13, 2020 at 05:21:48PM +0100, Thomas Danckaert wrote:
> As far as I remember,
> updates to texlive often seem to require the original texmf tarball and
> apply patches to it (not sure how this works precisely -- somehow there are
> no substitutes for the patched/updated version
Hi,
OH! I wasn't aware of the errors on avr-toolchain 5.5.
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/p7cs7wfvz26jyyr1qifkl68cr9i6
If I remember correctly, our avr-toolchain@5.5.0 package is broken, but
the avr-toolchain@4.9.4 package works. Could you try with
avr-toolchain@4.9.4 and see if the problem still persists? I
successfully built the QMK firmware some half a year ago, and I used the
avr-toolchain 4.9 to do it.
sign
Hi,
I'm having some issues with AVR toolchain.
I'm trying to compile QMK Firmware with Guix and it doesn't find the AVR header
files. Checking my profile installation I find there are not `include` files
for AVR-Libc.
Using guix edit avr-toolchain I read the following:
(define (avr-toolch
Hi Ricardo—
Je 22 feb 21:41 skribis Ricardo:
> > lualatex (from texlive-20180414) is looking in /usr/local/.
> >
> >
> > $ lualatex apen
> > This is LuaTeX, Version 1.07.0 (TeX Live 2018)
> > restricted system commands enabled.
> > (./apen.tex[
12 matches
Mail list logo
