From owner-freebsd-sparc Thu Feb 10 18:28: 6 2000 Delivered-To: freebsd-sparc@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by builder.freebsd.org (Postfix) with ESMTP id 96A2445D6 for ; Thu, 10 Feb 2000 18:26:18 -0800 (PST) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA86733 for ; Thu, 10 Feb 2000 18:25:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA61517; Thu, 10 Feb 2000 18:24:19 -0800 (PST) (envelope-from obrien) Date: Thu, 10 Feb 2000 18:24:19 -0800 From: "David O'Brien" To: Lyndon Griffin Cc: freebsd-sparc@freebsd.org Subject: Re: Cross-compiler question Message-ID: <20000210182419.C31201@dragon.nuxi.com> Reply-To: freebsd-sparc@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from lgriffin@bsd4us.org on Thu, Feb 10, 2000 at 12:49:43PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 10, 2000 at 12:49:43PM -0500, Lyndon Griffin wrote: > I have one question, and it's probably a stupid one, but it's got me > stumped... Scenario: I'm building the toolchain to install in > /usr/sparc. So far, I've had to copy /usr/include to /usr/sparc/include > and set appropriate flags in the makefiles. Everything seems to be going > ok, until I get into the actual gcc compiling. At this point, it seems > relectant to look in /usr/include or /usr/sparc/include for any of the > files that I've placed there. I keep having to hard-code things like Have you checked the GCC website and mailing lists to make sure you are following the correct steps in configuring for a cross-compiler? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message