From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Crosscompiling C++ for powerpc64le fails
Date: Fri, 31 May 2019 23:54:32 +0200 [thread overview]
Message-ID: <87tvdal27b.fsf@gnu.org> (raw)
In-Reply-To: <20190529121016.1c593a7c@scratchpost.org> (Danny Milosavljevic's message of "Wed, 29 May 2019 12:10:16 +0200")
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> I've investigated a bit more:
>
> Guix's gcc-4.7 passes
>
> (string-append "--with-native-system-header-dir=" libc "/include")
> where libc is (assoc-ref %build-inputs "libc")
>
> .
>
> However, further down, there is
>
> `(let* ((libc (assoc-ref %build-inputs "libc"))
> (libc-native (or (assoc-ref %build-inputs "libc-native")
> libc)))
>
>
> which makes me think that "--with-native-system-header-dir=" should use
> libc-native if the latter is present.
>
> It would be possible to pass "--with-headers=" to gcc which would make it copy
> the specified directory into the gcc installation directory and everything
> would work without weird workarounds.
You’re probably right, it would be worth giving it a try.
The weird thing is that:
guix build mpfr --target=arm-linux-gnueabihf
works fine on current master, which uses GCC 5.5 for cross-compilation.
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?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-05-31 22:05 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 [this message]
2019-06-03 18:30 ` Marius Bakke
2019-06-05 13:04 ` Ludovic Courtès
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=87tvdal27b.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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 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.