From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Ian Lance Taylor <iant@google.com>,
ams@gnu.org, gcc@gcc.gnu.org, 11034@debbugs.gnu.org,
gdb@sourceware.org, automake@gnu.org, binutils@sourceware.org,
joseph@codesourcery.com,
"automake-patches@gnu.org" <automake-patches@gnu.org>,
Roumen Petrov <bugtrack@roumenpetrov.info>
Subject: Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option
Date: Wed, 04 Apr 2012 07:43:00 -0000 [thread overview]
Message-ID: <4F7BFB80.7090406@gmail.com> (raw)
In-Reply-To: <87pqboft2j.fsf@fleche.redhat.com>
On 04/03/2012 10:39 PM, Tom Tromey wrote:
>>>>>> "Stefano" == Stefano Lattarini <stefano.lattarini@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:
>
Yes, but (at least for the binutils case) that's only because you already
have an hack *unrelated to the cygnus option* to make it work; i.e., in
'binutils/doc/Makefile.am', I read:
# Automake 1.9 will only build info files in the objdir if they are
# mentioned in DISTCLEANFILES. It doesn't have to be unconditional,
# though, so we use a bogus condition.
if GENINSRC_NEVER
DISTCLEANFILES = binutils.info
endif
> 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?
>
With the testcase attached to my mail (warning: it requires the Automake
testsuite infrastructure to work). I can transform it in an independent
test script if you are really interested.
> If you built from a distribution tar, then it is expected that the info
> file would be in srcdir.
>
I didn't use the binutils distribution to test my claim, but the minimal
test case I had created on purpose, and attached in the previous mail.
Regards,
Stefano
next prev parent reply other threads:[~2012-04-04 7:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 10:05 Stefano Lattarini
2012-03-28 11:25 ` Joseph S. Myers
2012-03-28 12:20 ` Stefano Lattarini
2012-03-28 12:29 ` Joseph S. Myers
2012-03-28 13:02 ` Stefano Lattarini
2012-03-28 23:43 ` Ian Lance Taylor
2012-03-31 8:30 ` bug#11034: " Stefano Lattarini
2012-03-31 9:08 ` Alfred M. Szmidt
2012-03-31 10:14 ` Stefano Lattarini
2012-04-04 13:18 ` Joseph S. Myers
2012-04-05 12:04 ` Stefano Lattarini
[not found] ` <4F76D8F2.8050804__46768.5595191599$1333188914$gmane$org@gmail.com>
2012-04-02 14:26 ` Tom Tromey
2012-04-02 15:04 ` Stefano Lattarini
2012-04-02 15:17 ` Tom Tromey
2012-04-02 15:30 ` Stefano Lattarini
[not found] ` <4F79C5F2.2020807__46832.8654104427$1333380662$gmane$org@gmail.com>
2012-04-02 19:37 ` Tom Tromey
2012-04-02 19:51 ` Stefano Lattarini
[not found] ` <4F7A0341.9050305__49963.8538728051$1333396325$gmane$org@gmail.com>
2012-04-02 20:19 ` Tom Tromey
2012-04-02 20:50 ` Stefano Lattarini
2012-04-02 21:10 ` Ian Lance Taylor
2012-04-03 20:04 ` Stefano Lattarini
2012-04-03 20:05 ` Stefano Lattarini
2012-04-03 20:29 ` Stefano Lattarini
2012-04-03 20:40 ` Tom Tromey
2012-04-04 7:43 ` Stefano Lattarini [this message]
2012-04-03 21:08 ` Ian Lance Taylor
2012-04-03 21:40 ` Pedro Alves
2012-04-03 23:53 ` Miles Bader
2012-04-04 7:47 ` Stefano Lattarini
2012-04-04 9:03 ` Pedro Alves
2012-04-03 8:23 ` Joern Rennecke
2012-03-31 11:39 ` Stefano Lattarini
2012-03-31 16:42 ` bug#11034: " Stefano Lattarini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7BFB80.7090406@gmail.com \
--to=stefano.lattarini@gmail.com \
--cc=11034@debbugs.gnu.org \
--cc=ams@gnu.org \
--cc=automake-patches@gnu.org \
--cc=automake@gnu.org \
--cc=binutils@sourceware.org \
--cc=bugtrack@roumenpetrov.info \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=joseph@codesourcery.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).