On Mon, Aug 06, 2012 at 06:37:07PM +0200, meino.cra...@gmx.de wrote:
> Paul Hartman [12-08-06 17:36]:
> > On Mon, Aug 6, 2012 at 8:01 AM, wrote:
> > > Hi,
> > >
> > > I am asking, because I found not only one description of somehow
> > > complicated setups to compile a distribution (namely gento
On Mon, 6 Aug 2012 15:01:40 +0200
meino.cra...@gmx.de wrote:
> So - is there any logical reason, which prevents the process of the
> compilation of a complete distribution/rootfs/boot-mechanism for
> a platform "A" on a hostsystem of the platform "B" if the cross
> compilation toolchain is alread
Paul Hartman [12-08-06 17:36]:
> On Mon, Aug 6, 2012 at 8:01 AM, wrote:
> > Hi,
> >
> > I am asking, because I found not only one description of somehow
> > complicated setups to compile a distribution (namely gentoo) for a
> > platform "A" (Beaglebone TI OMAP4) on that platform with distcc to
>
On Mon, Aug 6, 2012 at 8:01 AM, wrote:
> Hi,
>
> I am asking, because I found not only one description of somehow
> complicated setups to compile a distribution (namely gentoo) for a
> platform "A" (Beaglebone TI OMAP4) on that platform with distcc to
> speedup things or with emulated chroot envi
Hi,
I am asking, because I found not only one description of somehow
complicated setups to compile a distribution (namely gentoo) for a
platform "A" (Beaglebone TI OMAP4) on that platform with distcc to
speedup things or with emulated chroot environments based on qemu...
I thought it would be the
>
>
>I understand that too, but: whatever I compile in the chroot will have
>to run on my P4 for a while until it's done. Like the complete toolchain
>and some others. But if everybody says that's all fine I'll believe that.
>
>
My thought is the following: the system in the chroot utilizes the
Nick Rout wrote:
>whatever you do in the chroot will not affect your system outside the
>chroot (except where you have remounted stuff like /usr/portage and
>/proc)
>
>
Yes, I know and understand that.
>therefore you can set CFLAGS to whatever you like inside the chroot, and
>compile for athlo
whatever you do in the chroot will not affect your system outside the
chroot (except where you have remounted stuff like /usr/portage and
/proc)
therefore you can set CFLAGS to whatever you like inside the chroot, and
compile for athlon in there, leaving your P4 setup intact on your base
system.
I thought a bit about it and came to the conclusion that doing the
install just like normal is the way to go, all in a single dir
somewhere. For CFLAGS i will go with march=i686 and mtune=athlon-tbird,
think that will keep compatibility with my home setup and will also
optimize for remote arch.
Co
Nick Rout wrote:
>relatively simple. the general idea is thus:
>
>
Ok, thank you. The main concern I had were concerning the CFLAGS,
because I think after building say coreutils in the chroot for Athlon
they will not work any longer on my P4 but I need them in the chroot, no?
Jan
--
gentoo-use
Keziah W wrote:
>Maybe this will help?
>http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO
>
Interesting, I will read. Thank you!
Jan
--
gentoo-user@gentoo.org mailing list
Maybe this will help?
http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO
--
gentoo-user@gentoo.org mailing list
relatively simple. the general idea is thus:
1. make a directory, say
mkdir /mnt/target
2. untar a stage3 tarball into there, for the architecture you want.
3. mount various directories
mount -t proc none /mnt/target/proc
mount -o bind /usr/portage /mnt/target/usr/portage
cp /etc/resolv.conf /
Jan,
I think this is the same thing I want to know about. I run Gentoo
but want to try running it on my XBox. In general I am guessing we
handle it jsut like a normal install. Make a directory that will
represent the root of the new system, then chroot into it and work
only in there. That's just
Hello there,
I want to build a complete Gentoo system on my PC to save a friend the
time for compiling. The question I have is: what do I need to take care
of if my machine is a Pentium 4 and his is an Athlon? I know that if I
choose my CFLAGS like march=i686 the code will run on both machines, bu
15 matches
Mail list logo
