From: meino.cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] crosscompiling...the point of view
Date: Mon, 6 Aug 2012 15:01:40 +0200 [thread overview]
Message-ID: <20120806130140.GA4381@solfire> (raw)
Hi,
I am asking, because I found not only one description of somehow
complicated setups to compile a distribution (namely gentoo) for a
platform "A" (Beaglebone TI OMAP4) on that platform with distcc to
speedup things or with emulated chroot environments based on qemu...
I thought it would be the easiest to compile the whole stuff on a host
system "B" with a crosscompilation toolchain...but may be I have
overlooked something important...
So - is there any logical reason, which prevents the process of the
compilation of a complete distribution/rootfs/boot-mechanism for
a platform "A" on a hostsystem of the platform "B" if the cross
compilation toolchain is already installed on "B" and no emulated
environment is wanted?
Thank you very much in advance for any help!
Best regards,
mcc
next reply other threads:[~2012-08-06 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 13:01 meino.cramer [this message]
2012-08-06 15:30 ` [gentoo-user] crosscompiling...the point of view Paul Hartman
2012-08-06 16:37 ` meino.cramer
2012-08-07 13:36 ` YoYo Siska
2012-08-06 16:15 ` Daniel Wagener
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=20120806130140.GA4381@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.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