From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aron Griffis Subject: Re: [PATCH 1 of 2] Make tools/Makefile cross-friendly Date: Sat, 19 Jan 2008 10:33:05 -0500 Message-ID: <20080119153300.GB22728@fc.hp.com> References: <79cf8ffbc6678f201d35.1200715350@jenkins.nashua> <20080119144759.GA22728@fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20080119144759.GA22728@fc.hp.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org To follow up a bit more on the sys-root question, this web page explains it: http://benoit.papillault.free.fr/notes/cross-gcc.php.en The sys-root is built into both the compiler and binutils using the --with-sysroot option. That way the compiler can find the include files, and the linker can find the libraries. The cross-toolchain that I based mine on are from here: http://www.redhat.com/archives/fedora-devel-list/2007-October/msg00045.html These assume the sys-root will be in /usr/$target/sys-root, so that's how I set things up too. Lennert suggests using a script repack_cross.pl to install target rpms in the sys-root. I used that for a while but the number of rpms needed was overwhelming, so eventually I realized it would be a lot easier to use an entire root filesystem. For the rootfs, I started with fedora8/ia64 but it's missing some libs, so I switched to rhel5/ia64. For the howto, I intend to switch to centos4.6 so licensing isn't an issue. In any case, it's not hard to do a simple ia64 installation then bundle up the sys-root from it. Hope that helps, Aron