It would be nice if the Embedded guide included information on how to build a stage 1 for a new architecture, i.e what packages to cross compile, where to put them, creating a bootable environment, esp. if there are no stages available to use for that architecture, assuming the cross compiling toolchain is already available. Reproducible: Always
http://dev.gentoo.org/~vapier/PORTING-HOWTO
this issue isnt specific to embedded
Thanks very much for the PORTING HOWTO, I'll find it very useful for porting!
(In reply to comment #2) > this issue isnt specific to embedded It's not something the GDP plans to maintain though -- it seems perfectly suited to embedded. Or did you want porting-howto GuideXMLified and put in /doc/en?
whether embedded arches could use this guide is irrelevant. again, it is not specific to any arch. when people want to port to the Alpha or IA64 or Sparc or any other typical server/semi-desktop arch, they would not go to the embedded project. or if they wanted to port to an OS like FreeBSD or OpenSolaris or OpenBSD, they would not go to the embedded project. this information should live under doc/. my old PORTING-HOWTO should be guidexmlified and probably needs updating seeing as i slapped that together over four years ago.
I'd agree. I'm about to learn about porting to new archs and thought that the guide was one of the best places to start with but it is a bit out of date and there are no existing other distributions I can use to start the process. The list of things needed for a successful port needs to include things like ls, cp, mv, and ps etc.
we dont operate in terms of specific utilities. for a basic system, you need to `emerge system` which is an alias for the important packages -- coreutils, procps, etc...
Created attachment 234371 [details] porting-howto.xml Initial draft of porting-howto.xml. Mike, please review this for accuracy. I tried to update it where I could (default-linux/ to default/linux/ for example), but you have a better sense of what's too old. Also, to get the guide added, we really should have those scripts stored someplace besides a devspace, so that they don't get misplaced or deleted.
the profile stuff is out of date, and the catalyst should be reviewed to see if it needs updating. i'll try and post an updated file to cover that. otherwise the rest looks OK to me. the bootstrap-portage code probably can be updated, but that's independent of the doc.
(In reply to comment #9) > the profile stuff is out of date, and the catalyst should be reviewed to see if > it needs updating. i'll try and post an updated file to cover that. otherwise > the rest looks OK to me. > > the bootstrap-portage code probably can be updated, but that's independent of > the doc. Ping. What specifically needs doing?
I recommend putting this on the Gentoo wiki somewhere ;-)
