X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 8 Sep 2008 18:32:55 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Difficulty building gcc 4.3.2 under i386-pc-cygwin Message-ID: <20080908223255.GA18802@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1220909037 DOT 6401 DOT ezmlm AT cygwin DOT com> <20080908214759 DOT GA18503 AT ednor DOT casa DOT cgf DOT cx> <028301c91200$a6a37540$9601a8c0 AT CAM DOT ARTIMI DOT COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <028301c91200$a6a37540$9601a8c0@CAM.ARTIMI.COM> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Sep 08, 2008 at 11:17:16PM +0100, Dave Korn wrote: >Christopher Faylor wrote on 08 September 2008 22:48: > >> On Mon, Sep 08, 2008 at 09:43:37PM +0000, Jay wrote: >>> You can build gcc 4.3.1 and 4.3.2 just fine from the existing Cygwin gcc >>> 3.x package. >>> >>> The error also /appeared/ to have the object directory under the source >>> directory. Don't do that. >> >> Huh? There's no reason not to do this. I do it all of the time. > > It is unsupported: > >http://gcc.gnu.org/install/configure.html > >"... building where objdir is a subdirectory of srcdir is unsupported." What's that? An actual reference to a definitive source? Do you think that will ever catch on? I have been building gcc like that (and also in a completely separate directory) for many years, but if this officially unsanctioned then, nevermind. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/