From owner-freebsd-arch Wed Nov 17 21:59: 0 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 145E714A09 for ; Wed, 17 Nov 1999 21:58:57 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id GAA25728 for ; Thu, 18 Nov 1999 06:58:55 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA60708 for freebsd-arch@freebsd.org; Thu, 18 Nov 1999 06:58:55 +0100 (MET) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8A29714A09 for ; Wed, 17 Nov 1999 21:58:47 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA09780 for ; Wed, 17 Nov 1999 22:58:46 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA21245 for ; Wed, 17 Nov 1999 22:59:07 -0700 (MST) Message-Id: <199911180559.WAA21245@harmony.village.org> To: arch@freebsd.org Subject: Cross compilation goals. In-reply-to: Your message of "Wed, 17 Nov 1999 18:40:34 PST." <19991117184034.A53402@dragon.nuxi.com> References: <19991117184034.A53402@dragon.nuxi.com> <199911151707.JAA03820@freefall.freebsd.org> <199911160533.WAA02391@harmony.village.org> Date: Wed, 17 Nov 1999 22:59:07 -0700 From: Warner Losh Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In private Mail, David O'Brian asked the musical questions: : Would it be possible ... [to] discuss the issue and come up : with a unified plan? Either privately, or on the freebsd-arch list? Sure. Maybe it might be a good idea to start with goals. Everyone is working from different goals... Goals: 1) The ability to generate code for the target platform. The target platform may be a different architecture, or a different version of FreeBSD than the host system runs. 2) The ability to build tools to generate code for the target platform in a standard way. 3) The ability to install the cross tools. 4) The ability to specify a different set of tools easily so that one can do cross development, rather than just cross compilation. 5) Any methods will be documented 6) No impact on the non-cross compilation cases (eg, we can't break native builds) 7) Be useful for a buildworld replacement which will solve the problem of tools generating binaries to build the rest of the system that cannot run on the system at hand due to new kernel functionalty. Non-goal: 1) Have the cross compilation code necessarily work on other systems. I'd like to keep these goals simple and not let this get out of hand. But rather as a sanity check for those interested enough to have committed code to the efforts along the way. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message