On Wednesday 11 July 2007, [EMAIL PROTECTED] wrote: > Could someone please tell me how to build stages from scratch?
catalyst is used to build all stages [natively], from scratch is done by hand at the moment > I mean, I want to have gentoo installed into the new target that does > not have binary stage[123] released. > > Precisely, my target is sh3/sh4-nofpu, sh(SuperH) variant which has > no floating point arith. I know sh is not really new, but these > can not execute current sh (experimental)release, which is sh4 binary. we dont exactly have a document covering initial porting ... about the closest we have so far is: http://dev.gentoo.org/~vapier/PORTING-HOWTO i guess i should add some sections for how to bootstrap yourself using Gentoo ... > Now I'm trying to cross-build stage1 by xmerging each packages on PC. > But, It seems that I have to stop xmerging prematually, because there > are some packages which are difficult to cross build (like perl). > Perhaps, I will continue build natively with the incomplete stage > (stage0.5?) on the target, later. > > I wonder if it is right way or not. > What it should be? How really were currently released stages built? it's fine if you skip some packages like perl ... the critical things really are the toolchain (gcc/binutils/libc), portage (so python too), and the lowlevel utils (baselayout/gawk/sed/grep/etc...) once you have those, you should be able to boot up natively and finish doing `emerge` on the sh3 machine -mike
signature.asc
Description: This is a digitally signed message part.
