On 10 May 2014, at 05:12pm, Koornstra, Reinoud <koorns...@hp.com> wrote: > Hi Gary, > > I wonder even if you can do this: > > CLFS_TARGET32=i686-altimatos-linux-gnu > CLFS_HOST=x86_64-altimatos-linux-gnu > > I mostly put unknown there in case I build a build tool that HAS to work on > any powerpc or any x86_64 platform. > Thinking about you might just do this, but I would do it when you're building > the tools for the platform to boot itself. > This section: > III. Make the Cross-Compile Tools > > 5. Constructing Cross-Compile Tools > Isn't the place to start doing this. > You could try temporary system, but eventually, chapter 10 would be the place > to do this. > > Trying to make a system from scratch is VERY meticulous so I'd advise to use > the target and host only at chapter 10. > 10. Installing Basic System Software > Thanks, > > Reinoud. >
Been doing this for a LONG time with these as the tuples. The unknown field is your vendor field, which is legal to change to ANY string. -- Gary L. Greene, Jr. ================================================================================ Volunteer Developer for the AltimatOS and KDE F/OSS projects. Please refrain from sending me closed Please refrain from sending me closed office file formats (DOC, XLS, PPT). ================================================================================
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Clfs-support mailing list Clfs-support@lists.cross-lfs.org http://lists.cross-lfs.org/listinfo.cgi/clfs-support-cross-lfs.org