From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18888 invoked by alias); 10 May 2003 04:57:53 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18869 invoked from network); 10 May 2003 04:57:53 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by sources.redhat.com with SMTP; 10 May 2003 04:57:53 -0000 Received: from free.redhat.lsd.ic.unicamp.br (aoliva.cipe.redhat.com [10.0.1.10]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id h4A4voi05203; Sat, 10 May 2003 00:57:50 -0400 Received: from free.redhat.lsd.ic.unicamp.br (free.redhat.lsd.ic.unicamp.br [127.0.0.1]) by free.redhat.lsd.ic.unicamp.br (8.12.8/8.12.8) with ESMTP id h4A4vneQ015622; Sat, 10 May 2003 01:57:49 -0300 Received: (from aoliva@localhost) by free.redhat.lsd.ic.unicamp.br (8.12.8/8.12.8/Submit) id h4A4vnDH015618; Sat, 10 May 2003 01:57:49 -0300 To: DJ Delorie Cc: bkoz@redhat.com, gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com Subject: Re: srcdir == objdir build issues [SC take note] References: <20030509201035.51143c7d.bkoz@redhat.com> <200305100140.h4A1eKqB022183@envy.delorie.com> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Sat, 10 May 2003 04:57:00 -0000 In-Reply-To: <200305100140.h4A1eKqB022183@envy.delorie.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-05/txt/msg00178.txt.bz2 On May 9, 2003, DJ Delorie wrote: > It also added a maintenance headache for the "synthetic" top-level > Makefile, since every target in the real Makefile would have to be > replicated Not every target, only the standard ones, such as all, install, clean, possibly bootstrap. Or we could just finish ./configure by printing a message such as: since the build instructions suggest you should build in a directory separate from the source tree, we went ahead and created it for you. To build, cd to that directory and then make bootstrap or make all will work. This will break for people who automate it with ./configure; make; make install, but GCC has had a non-standard build procedure forever (we recommend make bootstrap, not make), and the error may actually be a good opportunity for people to actually read the installation instructions. Especially if the message actually points people at it. Hmm... But then, why not go ahead and just fail to configure anyway. Yeah... It makes sense as well. Maybe even more sense... -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer