From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6295 invoked by alias); 3 Apr 2012 08:23:22 -0000 Received: (qmail 6121 invoked by uid 22791); 3 Apr 2012 08:23:20 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from c60.cesmail.net (HELO c60.cesmail.net) (216.154.195.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Apr 2012 08:22:57 +0000 Received: from unknown (HELO delta2) ([192.168.1.50]) by c60.cesmail.net with ESMTP; 03 Apr 2012 04:22:40 -0400 Received: from host-92-29-209-134.as13285.net (host-92-29-209-134.as13285.net [92.29.209.134]) by webmail.spamcop.net (Horde MIME library) with HTTP; Tue, 03 Apr 2012 04:22:40 -0400 Message-ID: <20120403042240.s2mpkm8m8ggkw8oo-nzlynne@webmail.spamcop.net> Date: Tue, 03 Apr 2012 08:23:00 -0000 From: Joern Rennecke To: Stefano Lattarini Cc: Tom Tromey , ams@gnu.org, iant@google.com, gcc@gcc.gnu.org, 11034@debbugs.gnu.org, gdb@sourceware.org, automake@gnu.org, binutils@sourceware.org, joseph@codesourcery.com Subject: Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option References: <4F72E239.9010404@gmail.com> <4F7301DD.7090401@gmail.com> <4F76C08E.6050707@gmail.com> <4F76D8F2.8050804__46768.5595191599$1333188914$gmane$org@gmail.com> <87zkaujjn1.fsf@fleche.redhat.com> <4F79BFDB.1070904@gmail.com> <87ty12i2pd.fsf@fleche.redhat.com> <4F79C5F2.2020807__46832.8654104427$1333380662$gmane$org@gmail.com> <87hax2hqop.fsf@fleche.redhat.com> <4F7A0341.9050305__49963.8538728051$1333396325$gmane$org@gmail.com> <87d37pj39j.fsf@fleche.redhat.com> <4F7A10D7.8050908@gmail.com> In-Reply-To: <4F7A10D7.8050908@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.4) Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-04/txt/msg00028.txt.bz2 Quoting Stefano Lattarini : > By looking at the 'handle_texinfo_helper' function in the automake script, > I suspect adding a new Automake option 'info-in-builddir' (say) and an > handful of lines to the automake script might be enough to give you an easy > way to force the '.info' files to be generated in the builddir. But before > doing so, I'd like to understand why you want so strongly to support such > a setup. It is quite common during development / testing to build multiple configurations simultaneously from the same sources, with separate make processes. Writing to the source directory would cause disastrous race conditions.