From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: avr-gcc
Date: Thu, 14 Apr 2016 18:47:11 +0200 [thread overview]
Message-ID: <87twj4m92o.fsf@gnu.org> (raw)
In-Reply-To: <87h9f4spw3.fsf@drakenvlieg.flower> (Jan Nieuwenhuizen's message of "Thu, 14 Apr 2016 07:47:24 +0200")
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> From 5a6b6ba5a440d43af3e8c5cbd1d24f3be5a99804 Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke@gnu.org>
> Date: Sun, 27 Mar 2016 16:00:36 +0200
> Subject: [PATCH 1/9] gnu: gcc: use CPATH, fixes cross builds.
>
> * gnu/packages/gcc (gcc): Use CPATH instead of C_INCLUDE_PATH. Fixes usage of
> native glibc headers when cross-compiling.
This would be reverting the fix for <http://bugs.gnu.org/22186> as the
comment above explains.
I suppose the problem is that CPATH is still used elsewhere, leading to
interference with this one. However, the cross-compilers for
mips64el-linux-gnu and armhf-linux-gnueabi work fine, AFAIK.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-04-14 16:47 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 ` Ludovic Courtès [this message]
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 ` avr-gcc Ludovic Courtès
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=87twj4m92o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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.
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).