On Tue, Feb 27, 2007 at 09:37:22AM -0600, John Gnew wrote: > All, > > I am close to completing my LFS 6.2 port to s390. I have the system up > and running but need to verify a couple of items. > > So here is the question. > > What would be a recommendation on how to document this port into CLFS or > maybe its not a fit. This is not a cross compile which is what > everything in CLFS is. > Hi John,
from my pov, clfs is "the only game in town" for non-x86. Yes, messing with host and target to force a cross-compile on the same host is arguably unnecessary, but it's how the book works. These days, I only follow the 'boot' option when I need to test something there, but the book lets me successfully chroot. Looking at what is in trunk, the versions for your port of LFS-6.2 are somewhat out of date, so I guess you can't drop s390 straight in. Historically, new architectures have not always covered everything when they arrived in the book, but there is an expectation that the 'boot' option can be followed by the time they make it into a release. I don't know how realistic that is for s390, but if you are able to get it to build the packages already in the 'boot' chapter, plus whatever is specific to booting s390, then it should fit. As always, the details of how to transfer the data to the target machine if you really did cross-build are left to our users. I used to be a lowly application programmer on s390 and able to write the JCL to ftp data to other companies once our tech support guys set up the network/security side of things, so I guess that getting hold of the data for a new system is not an insurmountable problem for someone who already needs root access. Whether you really cross-compiled it is another matter entirely, and not really relevant! Of course, we'd have to change the index page in clfs trunk, we don't have any 31-bit systems at the moment ;) As you already know, most people working on the lfs and blfs books are not really interested in non-x86 these days, so you either need to 'get with the clfs program' (which probably means a willingness to continue to test changes from time to time), or continue to provide updated hints. From experience with ppc64, getting it all to fit together is possible, and I'm sure for someone of your experience it won't be too much of a big deal. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
