From: Chris Punches <chris.punches@silogroup.org>
To: crossgcc maillist <crossgcc@sourceware.org>
Subject: x86_64 cross-compiler
Date: Sun, 30 Aug 2020 21:53:38 -0400 [thread overview]
Message-ID: <f7192cde9b7995812af96f85a494af62cd0c825b.camel@silogroup.org> (raw)
Has anyone gotten an x86_64 cross-compiler successfully built with crosstool-ng?
If you did, would you mind providing your config? The samples do not appear to
work for various reasons.
My intent is to build a cross-compilation toolchain to `/opt/cross-compiler`,
and then build a native (multilib) compiler toolchain at `/opt/compiler`. From
there I'd like to use `/opt/compiler` to populate a chroot.
It sounds pretty simple, but, I could use some guidance as it is turning out to
be anything but.
-C
next reply other threads:[~2020-08-31 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 1:53 Chris Punches [this message]
2020-08-31 3:00 ` Chris Packham
2020-08-31 3:06 ` Chris Punches
2020-08-31 3:35 ` Chris Packham
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=f7192cde9b7995812af96f85a494af62cd0c825b.camel@silogroup.org \
--to=chris.punches@silogroup.org \
--cc=crossgcc@sourceware.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.
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).