From: Danny Milosavljevic <dannym@scratchpost.org>
To: Tobias Platen <trisquel@platen-software.de>
Cc: guix-devel@gnu.org
Subject: Re: Crosscompiling C++ for powerpc64le fails
Date: Tue, 28 May 2019 20:31:51 +0200 [thread overview]
Message-ID: <20190528203151.5b87be76@scratchpost.org> (raw)
In-Reply-To: <dd1dee2c-5cf7-e684-8631-78152f544f5b@platen-software.de>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hi Tobias,
On Tue, 28 May 2019 18:07:02 +0200
Tobias Platen <trisquel@platen-software.de> wrote:
> Im trying to cross compile basic GNU software such as bash and coreutils
> for powerpc.
>
> When building mpfr the build fails using the message above. I guess I
> have to specify the include paths for glibc to the configure script,
> since headers won't be found in /usr/include
We have a special Guix-specific patch for gcc which makes it heed these
environment variables:
* CROSS_C_INCLUDE_PATH
* CROSS_CPLUS_INCLUDE_PATH
* CROSS_LIBRARY_PATH
Try printing and/or setting those.
gnu/packages/cross-base.scm already contains a SEARCH-PATHS form in CROSS-GCC
which sets up the environment variables CROSS_LIBRARY_PATH,
CROSS_C_INCLUDE_PATH, CROSS_CPLUS_INCLUDE_PATH, CROSS_OBJC_INCLUDE_PATH,
CROSS_OBJCPLUS_INCLUDE_PATH, so it should have worked--but didn't.
That still leaves the libc. Not sure how it gets included in the environment
variables above.
See gnu/packages/admin.scm's sunxi-tools for a horrible workaround that
makes it work fine.
We should probably fix this problem.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-28 18:32 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 [this message]
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
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=20190528203151.5b87be76@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=trisquel@platen-software.de \
/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.