public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ed W <lists@wildgooses.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Cross emerging to a given root.
Date: Thu, 03 Dec 2009 16:50:49 +0000	[thread overview]
Message-ID: <4B17EC69.9090905@wildgooses.com> (raw)
In-Reply-To: <4B16C97C.2050709@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

Ryan Tandy wrote:
> Shinkan wrote:
>   
>> I emerged a cross-compiler on my host.
>> It's not to compile to a different arch than my host, but to compile
>> with given versions of glibc/binutils, to be sure that some bins will
>> run on my target system.
>>     
>
> If you aren't cross compiling, you could start a chroot using an
> appropriate stage for your target architecture.  Then once you had the
> appropriate toolchain set up in that chroot you could install packages
> in that chroot, build them there and merge them to a different ROOT, or
> even just build binary packages.  I don't think crossdev is necessary at
> all for what you're trying to do.
>
>   

As stated previously this is the "tiny gentoo" writeup on the gentoo 
wiki.  Works very nicely

Ed W

[-- Attachment #2: Type: text/html, Size: 1190 bytes --]

      reply	other threads:[~2009-12-03 18:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 17:46 [gentoo-embedded] Cross emerging to a given root Shinkan
2009-12-02 20:04 ` Peter Stuge
2009-12-03 14:21   ` Shinkan
2009-12-03 16:52     ` Ed W
2009-12-03 18:17       ` Shinkan
2009-12-03 23:23         ` Peter Stuge
2009-12-04  9:55         ` Ed W
2009-12-04 10:25           ` Peter Stuge
2009-12-03 23:19     ` Peter Stuge
2009-12-02 20:09 ` Ryan Tandy
2009-12-03 16:50   ` Ed W [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=4B17EC69.9090905@wildgooses.com \
    --to=lists@wildgooses.com \
    --cc=gentoo-embedded@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