public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] crosscompiling...the point of view
Date: Mon, 6 Aug 2012 10:30:16 -0500	[thread overview]
Message-ID: <CAEH5T2MF2Beueca9hvi8bowyTPDmHx3ygmtixm28ZhO3w=QKiA@mail.gmail.com> (raw)
In-Reply-To: <20120806130140.GA4381@solfire>

On Mon, Aug 6, 2012 at 8:01 AM,  <meino.cramer@gmx.de> wrote:
> 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...

Seems the best way to me, too.

> 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?

So you want to "install" the packages into a virtual filesystem image
on the compiler machine to create a whole disk image for the target,
basically? Hmmm. Maybe something like Scratchbox can help with this.


  reply	other threads:[~2012-08-06 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 13:01 [gentoo-user] crosscompiling...the point of view meino.cramer
2012-08-06 15:30 ` Paul Hartman [this message]
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='CAEH5T2MF2Beueca9hvi8bowyTPDmHx3ygmtixm28ZhO3w=QKiA@mail.gmail.com' \
    --to=paul.hartman+gentoo@gmail.com \
    --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