From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Crosscompiling C++ for powerpc64le fails
Date: Wed, 05 Jun 2019 15:04:47 +0200 [thread overview]
Message-ID: <878sug41zk.fsf@gnu.org> (raw)
In-Reply-To: <8736kq8qsc.fsf@devup.no> (Marius Bakke's message of "Mon, 03 Jun 2019 20:30:59 +0200")
Hi Marius,
Marius Bakke <mbakke@fastmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> The issue that Tobias reports reminds me of the CPATH vs. C_INCLUDE_PATH
>> issue that was causing troubles with newer GCCs, and that I think Marius
>> addressed in ‘core-updates’ (?). Marius, does that ring a bell?
>
> Unfortunately there are still issues with cross-compiling C++ on
> 'core-updates'. For 'C', the workaround was to go back to "CROSS_CPATH"
> instead of "CROSS_C_INCLUDE_PATH", like with native builds.
That should also address C++, since CPATH (and CROSS_CPATH) are for all
language front-ends, no just C, no?
> For native builds on core-updates, GCC7 occasionally fails if the libc
> or kernel headers are not on C_INCUDE_PATH (see e.g. f90d6c3). It could
> be that cross builds need a similar workaround, but I have not found the
> magic incantation yet.
How can it be that kernel headers are not on C_INCLUDE_PATH (or CPATH)?
On core-updates, I see that ‘gcc-6’ changes ‘native-search-paths’ from
C_INCLUDE_PATH & co. to CPATH, and likewise, ‘cross-gcc’ sets
‘search-paths’ to CROSS_CPATH. That looks consistent to me.
Ludo’.
next prev parent reply other threads:[~2019-06-05 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 16:07 Crosscompiling C++ for powerpc64le fails Tobias Platen
2019-05-28 18:31 ` Danny Milosavljevic
2019-05-29 10:10 ` Danny Milosavljevic
2019-05-31 21:54 ` Ludovic Courtès
2019-06-03 18:30 ` Marius Bakke
2019-06-05 13:04 ` Ludovic Courtès [this message]
2019-06-06 18:35 ` Marius Bakke
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=878sug41zk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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 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.