all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: 39794-done@debbugs.gnu.org
Subject: bug#39794: AVR-Toolchain-5 avr/io not found
Date: Sun, 01 Mar 2020 12:37:35 +0530	[thread overview]
Message-ID: <cu7v9no7du0.fsf@systemreboot.net> (raw)
In-Reply-To: <teqkfqKd4bxil3Yku25y4E4jS6VEDQ5c3jCzbfgEbKVMQi84OUB-Aleh2ZzhyumwddW1fSPf629LaUwAtNBUXm_HeGIqH-XmcPgvW3Ghl38=@elenq.tech>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]


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

Or, we could have separate environment variables CROSS_AVR_C_INCLUDE_PATH
and CROSS_ARM_C_INCLUDE_PATH. But that sounds like too many environment
variables! :-P

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

Something like this is possible too.

> We can start by pushing it and then keep solving the conflict issue
> and the upgrades to gcc-9.

Agreed.

>> 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?

I don't know. I have asked Danny at bug 24416 to push the patch. Let's
wait for a response.

Once Danny's patch is pushed, I'll open a new bug reporting the arm avr
conflict.

Also, I'm closing this bug report now since this issue is handled by
24416.

Thanks! :-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2020-03-01  7:08 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
2020-03-01  7:07                 ` Arun Isaac [this message]

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=cu7v9no7du0.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=39794-done@debbugs.gnu.org \
    --cc=ekaitz@elenq.tech \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.