Thanks for the excellent review, I'll rebase and implement the changes in my next coding session.
Michael E Brown <[EMAIL PROTECTED]> writes: > On Tue, Jun 12, 2007 at 09:15:13PM -0500, Ken MacLeod wrote: > Can you give an overview for the ignorant (ie. me) about the > difference between /cross and /target? Why is /cross its own > chroot-like thing? Couldnt you just say, "install this one > additional cross-buildsys-rpm, which pulls in the cross-toolchain?" I agree that that's the way it should work. You've got it right that the /cross tools are essentially part of the host environment, so the difference to /target is that target is the chroot for holding the target libraries and headers. Most cross-development toolkits assume their cross-tools install into a dedicated root and they don't do any renaming so they'd be replacing the equivalent host tools. A few do install themselves cleanly into /opt so I'll be able to test those without a cross root. RTEMS is built to install with RPM directly into the host filesystem under /opt, where MontaVista cross RPMs install under /opt but (I think) aren't set up to be in the host RPM db. When there's a good reference example for installing into the host filesystem (maybe RTEMS or MV) we can provide guidance for other distributions. -- Ken -- Fedora-buildsys-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
