unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Andy Wingo <wingo@pobox.com>, "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: avr-gcc
Date: Fri, 15 Apr 2016 23:10:45 +0200	[thread overview]
Message-ID: <87ega6shm2.fsf@gnu.org> (raw)
In-Reply-To: <878u0fs38f.fsf@drakenvlieg.flower> (Jan Nieuwenhuizen's message of "Fri, 15 Apr 2016 10:09:04 +0200")

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> Except for packages that need a native gcc to build tools during build
> time (CC_FOR_BUILD).  For such packages (like Bash or Guile),
> standard-packages must include gcc again.  Then, the build recipe's
> phases must be changed so that when cross compiling, the
> C_INCLUDE_PATH is moved into CPATH and C_INCLUDE_PATH is unset.
> That makes this solution even more unattractive, many changes
> to package recipe's could be needed.

Right!  That is really a bug, and I wonder why we didn’t catch it before
(maybe because the libc’s are pretty much the same in the systems we
were targeting?).

I had actually worked around it in
e8e2e18b84eb8842a59be9bf7d49bb672260ae3a in one particular case.

So the fix, as you suggest, is (1) to change
gcc-cross-environment-variables.patch to CROSS_ify the other environment
variables as well, and (2) to remove the unsetenv that was added in
e8e2e18b84eb8842a59be9bf7d49bb672260ae3a.

Could you give it a try?  :-)

Thanks for taking the time to explain!

Ludo’.

  parent reply	other threads:[~2016-04-15 21:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 15:25 avr-gcc Ricardo Wurmus
2015-11-17 15:59 ` avr-gcc Ricardo Wurmus
2015-11-17 21:32 ` avr-gcc Ludovic Courtès
2015-11-18  3:53   ` avr-gcc Thompson, David
2015-11-18 11:03     ` avr-gcc Ludovic Courtès
2015-11-19  1:54       ` avr-gcc Thompson, David
2015-11-20 14:20         ` avr-gcc Ludovic Courtès
2016-04-12 18:21           ` avr-gcc Thompson, David
2016-04-12 20:14             ` avr-gcc Thompson, David
2016-04-13 20:42             ` avr-gcc Ludovic Courtès
2016-04-14  5:47               ` avr-gcc Jan Nieuwenhuizen
2016-04-14 16:47                 ` avr-gcc Ludovic Courtès
2016-04-15  8:09                   ` avr-gcc Jan Nieuwenhuizen
2016-04-15  9:01                     ` avr-gcc Andy Wingo
2016-04-15 12:44                       ` avr-gcc Jan Nieuwenhuizen
2016-04-15 13:13                         ` avr-gcc Andy Wingo
2016-04-15 21:06                           ` avr-gcc Ludovic Courtès
2016-04-15 21:10                     ` Ludovic Courtès [this message]
2016-04-16 19:55                       ` avr-gcc Jan Nieuwenhuizen

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=87ega6shm2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@gnu.org \
    --cc=wingo@pobox.com \
    /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).