public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: 11034@debbugs.gnu.org
Cc: binutils@sourceware.org, gdb@sourceware.org, gcc@gcc.gnu.org,
	 Automake List <automake@gnu.org>
Subject: Binutils, GDB, GCC and Automake's 'cygnus' option
Date: Wed, 28 Mar 2012 10:05:00 -0000	[thread overview]
Message-ID: <4F72E239.9010404@gmail.com> (raw)

Hello.

I see that binutils, GCC and GDB still use the Automake's 'cygnus' option
in some of their makefiles:

  $ grep_cygnus() {
  >   grep -r 'cygnus' . \
  >    | perl -ne '/(^|[^@])cygnus($|(:!\.com\b))/ and print' \
  >    | grep -v '^[^:]*/Makefile\.in:'; \
  > }

  $ (cd ~/src/binutils && grep_cygnus) # BINUTILS
  ./bfd/doc/Makefile.am:AUTOMAKE_OPTIONS = 1.9 cygnus
  ./binutils/doc/Makefile.am:AUTOMAKE_OPTIONS = cygnus
  ./etc/configure.texi:AUTOMAKE_OPTIONS = cygnus
  ./gas/doc/Makefile.am:AUTOMAKE_OPTIONS = 1.8 cygnus

  $ (cd ~/src/gdb && grep_cygnus) # GDB
  ./bfd/doc/Makefile.am:AUTOMAKE_OPTIONS = 1.9 cygnus
  ./etc/configure.info:     AUTOMAKE_OPTIONS = cygnus
  ./etc/configure.texi:AUTOMAKE_OPTIONS = cygnus

  $ (cd ~/src/gcc && grep_cygnus) # GCC
  ./zlib/Makefile.am:AUTOMAKE_OPTIONS = 1.8 cygnus

But this option is going to be deprecated in Automake 1.12.1 and removed in
Automake 1.13:

  <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11034>

I just wanted to give you this head-up so that you won't be unpleasantly
surprised by the change.  Note that the actual removal of the 'cygnus'
option won't take place until Automake 1.13, which will at best be
released five or six months from now (and probably later than that).

Best regards,
  Stefano

             reply	other threads:[~2012-03-28 10:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 10:05 Stefano Lattarini [this message]
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
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=4F72E239.9010404@gmail.com \
    --to=stefano.lattarini@gmail.com \
    --cc=11034@debbugs.gnu.org \
    --cc=automake@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    /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).