public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: 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
Date: Mon, 02 Apr 2012 20:50:00 -0000	[thread overview]
Message-ID: <4F7A10D7.8050908@gmail.com> (raw)
In-Reply-To: <87d37pj39j.fsf@fleche.redhat.com>

On 04/02/2012 10:19 PM, Tom Tromey wrote:
>>>>>> "Stefano" == Stefano Lattarini <stefano.lattarini@gmail.com> writes:
> 
> Stefano> It should still be possible, with the right hack (which is
> Stefano> tested in the testsuite, and required by other packages
> Stefano> anyway).  The baseline is: if you don't want your '.info' files
> Stefano> to be distributed, then it should be easily possible to have
> Stefano> them built in the builddir; but if you want them distributed,
> Stefano> they will be built in the srcdir.
> 
> Now I am confused.  Is it possible to continue to work the way it does
> today, or not?
>
The point is: if you want to have info files build in the builddir *and*
distributed, than no, it won't be possible (without bending over backwards).
But I still don't understand why it's a big deal to have the '.info' files
placed in the srcdir *if you are going do distribute them*.

> If so, then great.
> 
> If not, then we need some other plan.
>
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.

> Tom> But, I see that, according to the Automake manual, I am wrong about that.
> 
> Stefano> Weird, I didn't expect that hack to be documented in the
> Stefano> manual...  And in fact I cannot find it.  Could you please
> Stefano> point me to it?  Thanks.
> 
>     http://www.gnu.org/software/automake/manual/automake.html#Cygnus
> 
> "Info files are always created in the build directory, and not in the
> source directory. Packages that don't use the cygnus option can emulate
> this effect by using the no-installinfo option and listing the generated
> info files in the CLEANFILES variable. "
> 
> Re-reading the suggestion here, I can't understand how it would work.
>
Another automake internal hack basically.  For more details, in case you are
interested, see code and comments in the 'automake.in:handle_texinfo_helper'
subroutine, and the test cases txinfo{23,24,25}.test in the Automake
distribution.

> Anyway the real use in the src tree is different, IIUC.
> Info files are built in the build tree by developers, but put in the
> source tree for distribution.
>
In such a setup, what is the issue with having the '.info' files built
in the srcdir?  It's not like the developers will develop with a
read-only source tree, right?

Regards,
  Stefano

  reply	other threads:[~2012-04-02 20:50 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 [this message]
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
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=4F7A10D7.8050908@gmail.com \
    --to=stefano.lattarini@gmail.com \
    --cc=11034@debbugs.gnu.org \
    --cc=ams@gnu.org \
    --cc=automake@gnu.org \
    --cc=binutils@sourceware.org \
    --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).