[gentoo-embedded] emerge ROOT question

[gentoo-embedded] emerge ROOT question

[Chris Bare]

When I specify ROOT before the emerge, it doesn't install any dependencies.
Why is this?
Is there some other flag I can give it to make it install dependencies?
-- 
Chris Bare
chris@bareflix.com
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] emerge ROOT question

[Mike Frisch]

On 6/16/06, Chris Bare <chris@bareflix.com> wrote:
> When I specify ROOT before the emerge, it doesn't install any dependencies.
> Why is this?
> Is there some other flag I can give it to make it install dependencies?

I've been wondering the same thing myself...  essentially, I want to
create a toolkit that will host a full Gentoo installation with all
dependencies without having to copy files from the host Gentoo
install.
-- 
gentoo-embedded@gentoo.org mailing list

Antwort: Re: [gentoo-embedded] emerge ROOT question

[andreas.sumper]

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

"Mike Frisch" <mikef17@gmail.com> schrieb am 06/16/2006 10:11:36 PM:

> On 6/16/06, Chris Bare <chris@bareflix.com> wrote:
> > When I specify ROOT before the emerge, it doesn't install any 
dependencies.
> > Why is this?
> > Is there some other flag I can give it to make it install 
dependencies?
> 
> I've been wondering the same thing myself...  essentially, I want to
> create a toolkit that will host a full Gentoo installation with all
> dependencies without having to copy files from the host Gentoo
> install.

just an idea:
What one could do, is building some sort of target-Filesystem and do a 
chroot into that system. Then the compiler has to be changed to your 
cross-compile-toolchain and some of the flags in make.conf have to be 
changed. After that, a simple emerge in the chrooted environmen should 
create all the needed stuff and cross-compile it for the specified 
architecture.

I will give it a try during the next weeks. It should work, but the 
correct values in make.conf and some of the includes and so on might be 
very hard to find out. At least, it will take a lot of time for testing 
and trying. But imho it should work. If someone manages to get this work, 
he/she might tell this list, as I guess, there are a bunch of people, who 
are interested in such things. (at least I am one of those *bg*)

Bye,
Andy

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

Re: Re: [gentoo-embedded] emerge ROOT question

[Mike Frisch]

On 6/17/06, andreas.sumper@cnsystems.at <andreas.sumper@cnsystems.at> wrote:
> just an idea:
> What one could do, is building some sort of target-Filesystem and do a
> chroot into that system. Then the compiler has to be changed to your
> cross-compile-toolchain and some of the flags in make.conf have to be
> changed. After that, a simple emerge in the chrooted environmen should
> create all the needed stuff and cross-compile it for the specified
> architecture.

Actually, this is pretty much what I'm doing already but I want to
wrap the process in a UI which will have issues with a chrooted
environment.

Thanks for the reply.
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] emerge ROOT question

[Chuck Robey]

Mike Frisch wrote:

> On 6/17/06, andreas.sumper@cnsystems.at <andreas.sumper@cnsystems.at> 
> wrote:
>
>> just an idea:
>> What one could do, is building some sort of target-Filesystem and do a
>> chroot into that system. Then the compiler has to be changed to your
>> cross-compile-toolchain and some of the flags in make.conf have to be
>> changed. After that, a simple emerge in the chrooted environmen should
>> create all the needed stuff and cross-compile it for the specified
>> architecture.
>
>
> Actually, this is pretty much what I'm doing already but I want to
> wrap the process in a UI which will have issues with a chrooted
> environment.
>
> Thanks for the reply.

Well, I want to be able to put together a Gentoo system but not to use 
Gentoo to do it, if that's remotely possible.  I rather like, for 
cross-building a system, the Pengutronix ptxdist stuff.  So, I can VERY 
easily use that to build all the normal Linux portions of a system, it's 
the Gentoo-specific parts (the stuff in /etc, and Portage, I *think* 
that;'s all) that I need to get built, and I don't even have a list of 
what the names of the pieces are, much less any idea where toget the 
sources from.

To be honst, from the Gentoo side of things, I'm pretty much at sea on 
this.  No idea how to even begin, although I know software well enough.  
Could you give me any ideas what the general path ahead of me is?  At 
the moment, I'm lookiing at a very messy job of trying to figure out the 
portions of my Pentium system will just copy over, and that seems 
incredibly wrong to try.  There has to be some central archive with  
Gentoo code somewhere, isn't there?
-- 
gentoo-embedded@gentoo.org mailing list

Antwort: Re: [gentoo-embedded] emerge ROOT question

[andreas.sumper]

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

Hi Chuck!

Chuck Robey <chuckr@chuckr.org> schrieb am 06/19/2006 06:47:55 PM:

> Mike Frisch wrote:
> 
> > On 6/17/06, andreas.sumper@cnsystems.at <andreas.sumper@cnsystems.at> 
> > wrote:
> >
> >> just an idea:
> >> What one could do, is building some sort of target-Filesystem and do 
a
> >> chroot into that system. Then the compiler has to be changed to your
> >> cross-compile-toolchain and some of the flags in make.conf have to be
> >> changed. After that, a simple emerge in the chrooted environmen 
should
> >> create all the needed stuff and cross-compile it for the specified
> >> architecture.
> >
> >
> > Actually, this is pretty much what I'm doing already but I want to
> > wrap the process in a UI which will have issues with a chrooted
> > environment.
> >
> > Thanks for the reply.
> 
> Well, I want to be able to put together a Gentoo system but not to use 
> Gentoo to do it, if that's remotely possible.  I rather like, for 
> cross-building a system, the Pengutronix ptxdist stuff.  So, I can VERY 
> easily use that to build all the normal Linux portions of a system, it's 

> the Gentoo-specific parts (the stuff in /etc, and Portage, I *think* 
> that;'s all) that I need to get built, and I don't even have a list of 
> what the names of the pieces are, much less any idea where toget the 
> sources from.
> 
> To be honst, from the Gentoo side of things, I'm pretty much at sea on 
> this.  No idea how to even begin, although I know software well enough. 
> Could you give me any ideas what the general path ahead of me is?  At 
> the moment, I'm lookiing at a very messy job of trying to figure out the 

> portions of my Pentium system will just copy over, and that seems 
> incredibly wrong to try.  There has to be some central archive with 
> Gentoo code somewhere, isn't there?

One thing you could try is creating a traget filesystem with ptxdist. So 
you would have at least an idea, which parts have to be put together and 
have a look, if you can find the equivalents in the portage-tree in 
gentoo. I guess that this should work. I tried ptxdist for myself, but 
creating the target-fs did not work properly, nor did the porting of 
Qt-embedded work correctly...
 
BTW, use busybox if possible, to keep your target small. This allows to 
use many commands with just one binary and some links.

Bye,
Andy

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

Re: Antwort: Re: [gentoo-embedded] emerge ROOT question

[Chuck Robey]

andreas.sumper@cnsystems.at wrote:

>
> Hi Chuck!
>
> Chuck Robey <chuckr@chuckr.org> schrieb am 06/19/2006 06:47:55 PM:
>
> > Mike Frisch wrote:
> >
> > > On 6/17/06, andreas.sumper@cnsystems.at <andreas.sumper@cnsystems.at>
> > > wrote:
> > >
> > >> just an idea:
> > >> What one could do, is building some sort of target-Filesystem and 
> do a
> > >> chroot into that system. Then the compiler has to be changed to your
> > >> cross-compile-toolchain and some of the flags in make.conf have to be
> > >> changed. After that, a simple emerge in the chrooted environmen 
> should
> > >> create all the needed stuff and cross-compile it for the specified
> > >> architecture.
> > >
> > >
> > > Actually, this is pretty much what I'm doing already but I want to
> > > wrap the process in a UI which will have issues with a chrooted
> > > environment.
> > >
> > > Thanks for the reply.
> >
> > Well, I want to be able to put together a Gentoo system but not to use
> > Gentoo to do it, if that's remotely possible.  I rather like, for
> > cross-building a system, the Pengutronix ptxdist stuff.  So, I can VERY
> > easily use that to build all the normal Linux portions of a system, 
> it's
> > the Gentoo-specific parts (the stuff in /etc, and Portage, I *think*
> > that;'s all) that I need to get built, and I don't even have a list of
> > what the names of the pieces are, much less any idea where toget the
> > sources from.
> >
> > To be honst, from the Gentoo side of things, I'm pretty much at sea on
> > this.  No idea how to even begin, although I know software well 
> enough.  
> > Could you give me any ideas what the general path ahead of me is?  At
> > the moment, I'm lookiing at a very messy job of trying to figure out 
> the
> > portions of my Pentium system will just copy over, and that seems
> > incredibly wrong to try.  There has to be some central archive with  
> > Gentoo code somewhere, isn't there?
>
> One thing you could try is creating a traget filesystem with ptxdist. 
> So you would have at least an idea, which parts have to be put 
> together and have a look, if you can find the equivalents in the 
> portage-tree in gentoo. I guess that this should work. I tried ptxdist 
> for myself, but creating the target-fs did not work properly, nor did 
> the porting of Qt-embedded work correctly...

Yeah, that's the method I intend to use, so far, and I'm working towards 
it right now, I think they've come a bit since you tried it, it seems to 
work now, although it's got bugs aplenty still.  It's the Gentoo parts 
that I need help on, I don't even have a clue how to begin for those.  
Not the Linix parts, in fact, I don't think I need even consider the 
busy box (and to be honest, I'd rather not, they are SO messed up!)

>  
> BTW, use busybox if possible, to keep your target small. This allows 
> to use many commands with just one binary and some links.
>
> Bye,
> Andy 


-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] emerge ROOT question

[Ned Ludd]

On Fri, 2006-06-16 at 15:07 -0400, Chris Bare wrote:
> When I specify ROOT before the emerge, it doesn't install any dependencies.
> Why is this?

When using the ROOT= variable emerge follows the RDEPEND's if you don't 
have the DEPEND's installed on the host / system. If they are not 
installed on the host / system then the direct DEPEND's will be 
installed to $ROOT. This is the expected behavior.

> Is there some other flag I can give it to make it install dependencies?

I find myself using ROOT=/somedir emerge -pvKe system when I need 
a full seed stage. you may also want to maybe check out the 
--deep/-D option.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list