From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Stefano Lattarini <stefano.lattarini@gmail.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
Subject: Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option
Date: Wed, 04 Apr 2012 13:18:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1204041313510.25863@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4F76D8F2.8050804@gmail.com>
On Sat, 31 Mar 2012, Stefano Lattarini wrote:
> 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.
The approach used in GCC, for example in the libquadmath directory, is a
--enable-generated-files-in-srcdir configure option that is used when
building a release tarball - so normally the files go in the build
directory, but a special configuration is used to put them in the source
directory only when building releases. (This does not involve the
"cygnus" option.) I think support for that seems more generically useful
(and it makes sense to me for automake to look at features used in other
packages' configure/build systems, that aren't inherently specific to
those packages, and try to provide generic versions of them).
The Binutils/GDB release tarball building process is substantially
different and I'm not familiar with it.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-04-04 13:18 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 [this message]
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=Pine.LNX.4.64.1204041313510.25863@digraph.polyomino.org.uk \
--to=joseph@codesourcery.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=stefano.lattarini@gmail.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