GNU bug report logs - #11034
Removing 'cygnus' mode in the near future

Previous Next

Full log

Message #89 received at 11034 <at> debbugs.gnu.org (full text, mbox):

From: Tom Tromey <tromey <at> redhat.com>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: gcc <at> gcc.gnu.org, Roumen Petrov <bugtrack <at> roumenpetrov.info>,
	11034 <at> debbugs.gnu.org, gdb <at> sourceware.org,
	Ian Lance Taylor <iant <at> google.com>,
	"automake-patches <at> gnu.org" <automake-patches <at> gnu.org>,
	automake <at> gnu.org, ams <at> gnu.org, binutils <at> sourceware.org,
	joseph <at> codesourcery.com
Subject: Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option
Date: Tue, 03 Apr 2012 14:39:48 -0600

>>>>> "Stefano" == Stefano Lattarini <stefano.lattarini <at> gmail.com> writes:

Stefano> On a second though, by double-checking the existing code, I
Stefano> couldn't see how the 'cygnus' option could possibly influence
Stefano> the location of the generated info files -- and it turned out
Stefano> it didn't!  Despite what was documented in the manual, the
Stefano> 'cygnus' option did *not* cause the generated '.info' files to
Stefano> be placed in the builddir (see attached test case).

It certainly does for me:

    barimba. pwd
    /home/tromey/gnu/baseline-gdb/build/binutils
    barimba. grep '^srcdir = ' Makefile
    srcdir = ../../src/binutils
    barimba. find . -name 'binutils.info'
    ./doc/binutils.info
    barimba. find ../../src/binutils -name 'binutils.info'
    barimba.

How did you test it?
If you built from a distribution tar, then it is expected that the info
file would be in srcdir.

Tom

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.