all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: libstdc++ for cross compilers
Date: Sun, 21 May 2017 15:09:13 +0200	[thread overview]
Message-ID: <87tw4egxvq.fsf@elephly.net> (raw)
In-Reply-To: <8760gvq1oi.fsf@elephly.net>


Ricardo Wurmus <rekado@elephly.net> writes:

> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>> I created a package variant like this:
>>
>> --8<---------------cut here---------------start------------->8---
>> (define-public libstdc++-arm-none-eabi
>>   (let* ((xgcc gcc-arm-none-eabi-6)
>>          (libstdc++ (make-libstdc++ xgcc)))
>>     (package (inherit libstdc++)
>>       (name "libstdc++-arm-none-eabi")
>>       (arguments
>>        (substitute-keyword-arguments (package-arguments libstdc++)
>>          ((#:configure-flags flags)
>>           ``("--target=arm-none-eabi"
>>              "--disable-libstdcxx-pch"
>>              ,(string-append "--with-gxx-include-dir="
>>                              (assoc-ref %outputs "out")
>>                              "/arm-none-eabi/include"))))))))
>> --8<---------------cut here---------------end--------------->8---
>>
>> And adding it to the inputs for the Axoloti firmware seems to be fine
>> for a while until it fails to find headers with “#include_next”.  I’ll
>> try to gather some better error messages.

The problem turned out to be right there: the configure flags set
“--target” but not “--host”, so libstdc++ wasn’t cross-built.

I have already overcome the problem and will submit a couple of patches
in the coming days.

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

      reply	other threads:[~2017-05-21 13:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 13:24 libstdc++ for cross compilers Ricardo Wurmus
2017-04-12  9:24 ` Ludovic Courtès
2017-04-13  8:54   ` Ricardo Wurmus
2017-05-20 10:10     ` Ricardo Wurmus
2017-05-21 13:09       ` Ricardo Wurmus [this message]

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=87tw4egxvq.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=ludo@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.