unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: "39794@debbugs.gnu.org" <39794@debbugs.gnu.org>
Subject: bug#39794: AVR-Toolchain-5 avr/io not found
Date: Sat, 29 Feb 2020 21:19:43 +0000	[thread overview]
Message-ID: <teqkfqKd4bxil3Yku25y4E4jS6VEDQ5c3jCzbfgEbKVMQi84OUB-Aleh2ZzhyumwddW1fSPf629LaUwAtNBUXm_HeGIqH-XmcPgvW3Ghl38=@elenq.tech> (raw)
In-Reply-To: <cu71rqd86s7.fsf@systemreboot.net>


> > I can replicate what you did and it works.
>
> Nice! :-)
>
> > May it be conflicting with other packages?
>
> arm-none-eabi-toolchain is conflicting with avr-toolchain since both are
> setting the CROSS_* environment variables. See the output of `avr-gcc -E -v -` below.
>
> This should probably be considered a bug. But I have no idea how to fix
> this. :-( What do you think?

I agree. The problem I see here is the environment variable game we have here.
One option is to create cross compilers with the include paths inserted on them instead of taking environment variables as a default.

If they had the correct directories in their default includepaths everything would work correctly.

I never did this before but it should be possible, probably affecting cross-gcc's configure step.

> Also, our avr-gcc package should probably be updated to the latest
> avr-gcc-9.

Once the current fix is applied next fixes should be possible.

Why wasn't the patch included in the project?
We can start by pushing it and then keep solving the conflict issue and the upgrades to gcc-9.

Have to say that nature of Guix makes the conflict issue easy to avoid while we find a solution for it.

  reply	other threads:[~2020-02-29 21:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 22:12 bug#39794: AVR-Toolchain-5 avr/io not found Ekaitz Zarraga
2020-02-26  8:44 ` Ekaitz Zarraga
2020-02-28 22:42   ` Ekaitz Zarraga
2020-02-29 15:06     ` Arun Isaac
2020-02-29 15:46       ` Ekaitz Zarraga
2020-02-29 15:58         ` Ekaitz Zarraga
2020-02-29 19:14         ` Arun Isaac
2020-02-29 19:26           ` Ekaitz Zarraga
2020-02-29 20:42             ` Arun Isaac
2020-02-29 21:19               ` Ekaitz Zarraga [this message]
2020-03-01  7:07                 ` 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='teqkfqKd4bxil3Yku25y4E4jS6VEDQ5c3jCzbfgEbKVMQi84OUB-Aleh2ZzhyumwddW1fSPf629LaUwAtNBUXm_HeGIqH-XmcPgvW3Ghl38=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=39794@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).