public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] How to manage multiple distributions, cross compilers in one chroot environment
Date: Thu, 6 Jan 2011 12:07:51 +0200	[thread overview]
Message-ID: <AANLkTikEpo04V9Woz29ziOnas9xStRf7VSPtJEa89V=j@mail.gmail.com> (raw)

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

Hi,
Continueing the discussion started by my last thread "CBUILD= HOSTCC=-gcc",
I said I want to compile a cross compiler with a special name.
I wanted i686-gentoo.edge-linux-gnu but it is possible to do just
i686-pc-linux-gnu

I did this because crossdev creates some magic setting up things, and it is
very handy.
What I want is a way to keep few compilers environments.
lets say:
stable x86 compiler
unstable x86 compiler
few arm cross compilers.

So when I create a distribution and an few month time I want the same
exactly environment,
to compile and upgrade few packages and be sure not to break anything, I
want to keep
those version of the compilers.

I'll also need some way to have few forks of my initial system.
lets say:
emebedded board 1 - for customer A
emebedded board 1 - for customer B (it is different than A, by time of
creation and so by version of the compiler used).
emebedded board 2 - for customer C

Can we boost up crossdev, or I need to start hacking a distro_creator
utility for gentoo?

Regards,
Kfir

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

             reply	other threads:[~2011-01-06 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 10:07 Kfir Lavi [this message]
2011-01-06 14:01 ` [gentoo-embedded] How to manage multiple distributions, cross compilers in one chroot environment Peter Stuge
2011-01-07 18:29   ` Kfir Lavi
2011-01-07 20:03     ` Peter Stuge
2011-02-05 15:34     ` Enrico Weigelt

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='AANLkTikEpo04V9Woz29ziOnas9xStRf7VSPtJEa89V=j@mail.gmail.com' \
    --to=lavi.kfir@gmail.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