From owner-freebsd-questions Tue Oct 15 14:34:56 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7180537B401 for ; Tue, 15 Oct 2002 14:34:55 -0700 (PDT) Received: from alpha.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20D6843EAA for ; Tue, 15 Oct 2002 14:34:54 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: from kenshin.yumyumyum.org (ken.yumyumyum.org [192.168.0.2]) by alpha.yumyumyum.org (8.12.6/8.12.5) with ESMTP id g9FLXXof072455; Tue, 15 Oct 2002 17:33:33 -0400 (EDT) (envelope-from culverk@yumyumyum.org) Content-Type: text/plain; charset="iso-8859-1" From: Kenneth Culver To: Deepankar Das Subject: Re: Building FreeBSD 4.6 with GCC 3.2 Date: Tue, 15 Oct 2002 17:34:39 -0400 User-Agent: KMail/1.4.3 References: <3C23AF6E.90202@ns.aus.com> <20011221164429.U48837@elvis.mu.org> <3DAC84D3.5010103@panasas.com> In-Reply-To: <3DAC84D3.5010103@panasas.com> Cc: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200210151734.39677.culverk@yumyumyum.org> X-Spam-Status: No, hits=-1.6 required=5.0 tests=IN_REP_TO,NO_MX_FOR_FROM,AWL version=2.31 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday 15 October 2002 05:12 pm, Deepankar Das wrote: > All, > > Has anyone tried building FreeBSD 4.6 with GCC 3.2? I am seeing > pre-processor problems during the "make depend" stage. Anything > that I need to know to make GCC 3.2 build FreeBSD 4.6? > > Thanks, > Deepankar I'm just curious, but why are you doing this. This isn't a supported way = of=20 doing things in FreeBSD 4.6, and I doubt that anyone's going to be able t= o=20 tell you how to do it because of that. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message