From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] How to manage multiple distributions, cross compilers in one chroot environment
Date: Fri, 7 Jan 2011 20:29:21 +0200 [thread overview]
Message-ID: <AANLkTinwvZCKeXr4FKxBh9B1OG-RuTzKn0Tw2YPEuVOc@mail.gmail.com> (raw)
In-Reply-To: <20110106140116.9767.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Thu, Jan 6, 2011 at 4:01 PM, Peter Stuge <peter@stuge.se> wrote:
> Kfir Lavi wrote:
> > 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.
> ..
> > Can we boost up crossdev,
>
> No boosting neccessary. Just use crossdev with some explicit version
> numbers for all components, and you get excellent repeatability.
>
> Ok, lets say I create a special crossdev. I still get it in
/usr/i686-pc-linux-gnu,
which is very generic.
Can't I have few compilers at a time?
> As for distro creater, I use catalyst to build a stage4 and stage5.
> Not sure how well that works for cross platform however, I only use
> on amd64 to build for various x86, and this may be a special case.
>
> I'll take a look on catalyst.
Can you refer me to a good introduction/manual ?
The gentoo page is not enough for me.
>
> //Peter
>
>
[-- Attachment #2: Type: text/html, Size: 1985 bytes --]
next prev parent reply other threads:[~2011-01-07 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 10:07 [gentoo-embedded] How to manage multiple distributions, cross compilers in one chroot environment Kfir Lavi
2011-01-06 14:01 ` Peter Stuge
2011-01-07 18:29 ` Kfir Lavi [this message]
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=AANLkTinwvZCKeXr4FKxBh9B1OG-RuTzKn0Tw2YPEuVOc@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