From: raingloom <raingloom@riseup.net>
To: John Soo <jsoo1@asu.edu>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: Cross gcc-toolchain
Date: Sat, 12 Sep 2020 12:03:13 +0200 [thread overview]
Message-ID: <20200912120313.142734a9@riseup.net> (raw)
In-Reply-To: <990C1374-DDF4-46FF-9482-BC664BB52F41@asu.edu>
On Thu, 10 Sep 2020 07:27:39 -0700
John Soo <jsoo1@asu.edu> wrote:
> Hi Guix,
>
> I am looking into ghc on ARM and the process seems like it only
> requires a separate gcc toolchain specified during configure. I have
> not packaged a gcc-toolchain yet, so I am looking for pointers. Would
> the gcc toolchain for cross compiling (say, from x86 to aarch64) be
> as simple as providing the target flag to the various toolchain
> packages’ configures?
>
> Thanks for your help!
>
> John
I tried packaging devkitARM (GCC 10 based version) and failed, so your
mileage may vary. I've never developed for ARM before, maybe it's
easier if you're a seasoned pro.
next prev parent reply other threads:[~2020-09-12 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 14:27 Cross gcc-toolchain John Soo
2020-09-12 10:03 ` raingloom [this message]
2020-09-12 13:56 ` John Soo
2020-09-15 19:44 ` raingloom
2020-09-16 1:55 ` John Soo
2020-09-16 18:15 ` raingloom
2020-09-16 22:32 ` John Soo
2020-09-17 0:59 ` raingloom
2020-09-17 1:07 ` John Soo
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=20200912120313.142734a9@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=jsoo1@asu.edu \
/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.
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).