From: Miles Bader <miles@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: Stefano Lattarini <stefano.lattarini@gmail.com>,
Ian Lance Taylor <iant@google.com>,
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 23:53:00 -0000 [thread overview]
Message-ID: <87fwck4bkk.fsf@catnip.gol.com> (raw)
In-Reply-To: <4F7B6E2B.2080504@redhat.com> (Pedro Alves's message of "Tue, 03 Apr 2012 22:39:55 +0100")
Pedro Alves <palves@redhat.com> writes:
>> OK, you've all made clear you have your sensible reasons to have the '.info'
>
> ...
>> it available only though the new, undocumented option named (literally)
>> "hack!info-in-builddir". I hope this is acceptable to you.
> ...
>> *undocumented* option '!hack!info-in-builddir' (whose name should
>> made it clear that it is not meant for public consumption).
>
> So will this be called a hack forever, or will the naming be revisited
> before a release? IMO, either the feature is sensible, and there doesn't
> seem to be a good reason other users couldn't also use it, and hence it
> should get a non-hackish name and be documented; or it isn't sensible, and
> then it shouldn't exist. Why the second-class treatment?
I suspect there are better, cleaner, ways to accomplish the underlying
goal, but I suppose the gcc maintainers don't want to spend the time
fiddling around with their build infrastructure for such a minor
issue...
-miles
--
Alone, adj. In bad company.
next prev parent reply other threads:[~2012-04-03 23:53 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
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 [this message]
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=87fwck4bkk.fsf@catnip.gol.com \
--to=miles@gnu.org \
--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=palves@redhat.com \
--cc=stefano.lattarini@gmail.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