public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: ams@gnu.org
Cc: 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: Sat, 31 Mar 2012 10:14:00 -0000	[thread overview]
Message-ID: <4F76D8F2.8050804@gmail.com> (raw)
In-Reply-To: <E1SDuIY-0004aQ-0U@fencepost.gnu.org>

Hi Alfred.

On 03/31/2012 11:08 AM, Alfred M. Szmidt wrote:
>      - Have them distributed (automake's default).  This means that
>        they will be build in the srcdir, not in the builddir: of
>        course, this only affects the maintainer, since for a user that
>        builds the package from a tarball those files should *not* be
>        rebuilt, hence there is no problem even if the user's srcdir is
>        read-only.
> 
> This has always been the right way to do things.
> 
>      - Don't distribute the generated info files.  [...]  In this
>        case, the user will have to to have the 'makeinfo' program
>        available to build them.
> 
> Please don't do this, it causes all kinds of headaches, like the small
> fact that makeinfo will now be required to bootstrap.
>
Note there's nothing I'm planning to do, nor I should do, in this regard:
the two setups described above are both already supported by the current
automake implementation (but the last one is not encouraged, even though
it makes perfect sense in some *rare* situations).  I was just pointing
out that you have to choose one of these setups -- so, if you want to
distribute info files, you must accept to have them build in the srcdir.

Regards,
  Stefano

  reply	other threads:[~2012-03-31 10:14 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 [this message]
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
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=4F76D8F2.8050804@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 \
    /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).