From owner-freebsd-hackers Wed Feb 19 21:48:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA19425 for hackers-outgoing; Wed, 19 Feb 1997 21:48:58 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA19417 for ; Wed, 19 Feb 1997 21:48:55 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vxRN8-0006t8-00; Wed, 19 Feb 1997 22:48:46 -0700 To: Don Yuniskis Subject: Re: GCC cross compiles Cc: freebsd-hackers@freefall.freebsd.org (FreeBSD hackers) In-reply-to: Your message of "Wed, 19 Feb 1997 18:00:40 MST." <199702200100.SAA10423@seagull.rtd.com> References: <199702200100.SAA10423@seagull.rtd.com> Date: Wed, 19 Feb 1997 22:48:46 -0700 From: Warner Losh Message-Id: Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199702200100.SAA10423@seagull.rtd.com> Don Yuniskis writes: : However, am I correct in assuming that one can safely build : *cross* compilers under reasonably recent FBSD releases using : the latest GCC sources (i.e. host=FBSD2.1R, target=68k)? : Has anyone done this and had decent success? I've done this with the raw gcc/binutils distribution, with the cygnus release and the OpenBSD tree. Forget it with the gcc/binutils in the freebsd tree, they are intel only. However, once you get the full sources, it generally is as simple as doing ./configure --target=mips-unknown-openbsd2.0 --host=i386-unknown-freebsd2.2 followed by a make. You'll need to arrange for include files and libraries, but that isn't too hard. Check out http://www.village.org/villagers/imp/build.html for something I wrote up a while ago on how to do this for Linux/MIPS. Warner