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: Re: [gentoo-embedded] Gentoo embedded handbook - wrappers
Date: Wed, 3 Nov 2010 12:27:54 +0200	[thread overview]
Message-ID: <AANLkTim0F2STEWmLTGRYpPCUTqF_L7jZODSdD6FDLj42@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinYUPKGQ+nABbES55sOYvk8-o6_a1POCuJ8VE7j@mail.gmail.com>

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

I don't know why, but I didn't have this emerge-wrappers. Now I do have it,
and I ran emerge-wrapper --init before the compilation.
Why it is needed and what does it do?

What will happen if I compile stuff for the target without running
emerge-wrapper?

Regards,
Kfir

On Mon, Nov 1, 2010 at 12:21 PM, Sven Rebhan <odinshorse@googlemail.com>wrote:

> emerge-wrapper still exists and is used, so I think your understanding
> is wrong. ;-)
>
> Regards,
>
>    Sven
>
> 2010/10/28 Kfir Lavi <lavi.kfir@gmail.com>:
> > Hi,
> > I have read the handbook and it seems to me that the section
> > "3.c. Intro: crossdev's wrappers" in the book
> >
> http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=3
> > Is a bit obsolete.
> >
> > Note: Before beginning any cross-emerge, you'll need to run
> > emerge-wrapper --init. Be sure to follow any instructions printed by
> > emerge-wrapper before beginning your cross-emerge.
> >
> > To my understanding there is no emerge-wrapper anymore.
> >
> > Regards,
> > Kfir
> >
> >
>
>

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

      reply	other threads:[~2010-11-03 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 12:44 [gentoo-embedded] Gentoo embedded handbook - wrappers Kfir Lavi
2010-11-01 10:21 ` Sven Rebhan
2010-11-03 10:27   ` Kfir Lavi [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=AANLkTim0F2STEWmLTGRYpPCUTqF_L7jZODSdD6FDLj42@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