public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Tom Tromey <tromey@redhat.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: Tue, 03 Apr 2012 20:29:00 -0000	[thread overview]
Message-ID: <4F7B5DA1.9000908@gmail.com> (raw)
In-Reply-To: <4F7B580F.2060007@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

On 04/03/2012 10:05 PM, Stefano Lattarini wrote:
> On 04/03/2012 10:04 PM, Stefano Lattarini wrote:
>> OK, you've all made clear you have your sensible reasons to have the '.info'
>> files generated in the builddir in your use cases.  Since the actual change
>> required by automake to allow this is very small and safe, I'm ready to do
>> it (see attached patch, which I will push in a couple of days to 'master' if
>> there is no objection).
>>
>> But since I'm not yet ready to publish this new feature, I intend to make
>> it available only though the new, undocumented option named (literally)
>> "hack!info-in-builddir".  I hope this is acceptable to you.
>>
On a second though, by double-checking the existing code, I couldn't see how
the 'cygnus' option could possibly influence the location of the generated
info files -- and it turned out it didn't!  Despite what was documented in
the manual, the 'cygnus' option did *not* cause the generated '.info' files
to be placed in the builddir (see attached test case).  This is true for at
least for automake 1.9.6, 1.10.3, 1.11.1, 1.11.4, and automake built from
the master branch (I've checked them all).  Since nobody ever complained
about such a breakage, I conclude that the feature was not truly needed, and
I'm thus withdrawing my previous patch.

Regards,
  Stefano

[-- Attachment #2: txinfo-cygnus-bug.test --]
[-- Type: text/plain, Size: 1224 bytes --]

#! /bin/sh
# Copyright (C) 2012 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program.  If not, see <http://www.gnu.org/licenses/>.

# The cygnus option do not really cause the '.info' files to be
# generated in the builddir!

required=makeinfo
. ./defs || Exit 1

cat >> configure.ac <<END
AM_MAINTAINER_MODE
AC_OUTPUT
END

cat > Makefile.am << 'END'
AUTOMAKE_OPTIONS = cygnus -Wno-override
info_TEXINFOS = foo.texi
END

cat > foo.texi << 'END'
\input texinfo
@setfilename foo.info
@settitle foo
@node Top
Hello walls.
@bye
END

$ACLOCAL
$AUTOMAKE --add-missing
$AUTOCONF

mkdir build
cd build
../configure
$MAKE info
ls -l . ..
test -f foo.info
test ! -f ../foo.info

:

  reply	other threads:[~2012-04-03 20:29 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:17             ` 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:25             ` Tom Tromey
2012-04-02 15:04               ` Stefano Lattarini
2012-04-02 15:16                 ` Tom Tromey
2012-04-02 15:30                   ` Stefano Lattarini
     [not found]                   ` <4F79C5F2.2020807__46832.8654104427$1333380662$gmane$org@gmail.com>
2012-04-02 19:36                     ` 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 [this message]
2012-04-03 20:40                                     ` Tom Tromey
2012-04-04  7:43                                       ` Stefano Lattarini
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=4F7B5DA1.9000908@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).