From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Gabriel Krisman Bertazi <gabriel@krisman.be>,
Pedro Alves <palves@redhat.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4 0/4] catch syscall group
Date: Tue, 12 May 2015 23:26:00 -0000 [thread overview]
Message-ID: <874mnhjs22.fsf@redhat.com> (raw)
In-Reply-To: <CADPb22SfGPtV0CoOjWitDfonziHYXT1ZofCBv270pWXtmuy3Gw@mail.gmail.com> (Doug Evans's message of "Tue, 12 May 2015 15:44:14 -0700")
On Tuesday, May 12 2015, Doug Evans wrote:
>> What exactly are you refering to? Generating the XML files using
>> xsltproc when compiling GDB? I will assume this in the rest of the
>> message, but if that's not what you meant, then please disconsider.
>
> Ah. I figured people know what --enable-maintainer-mode is. :-)
I always knew GDB had it, but I confess I never tried it myself.
> --enable-maintainer-mode is a configure time option that turns
> on some makefile dependency checking that is normally off.
> It is used, for example, to automagically regenerate configure
> when configure.ac changes, and only when make's
> standard processing says they need regenerating: i.e.,
> when the timestamp of the generated file is older than a timestamp
> of one of its dependencies.
>
> What happens if the user doesn't supply --enable-maintainer-mode
> when configuring? [which is the norm]
> Then the dependencies are turned off and no automagic regeneration
> is done (which is what one would want for a default).
Right, thanks for explaining. I don't know if a lot of people use this
or not (it seems to me that they don't), but yeah, since we have it...
>> I don't necessarily oppose hooking the XML generation into the
>> --enable-maintainer-mode option, but I'm having the impression that we
>> are bloating this feature more and more, without much gain. Unless I'm
>> really blind to some benefit, in which case I apologize in advance.
>
> What I'm asking for is trivial to do (there's already boilerplate
> to cut-n-paste-n-tweak form), *and* it is s.o.p.
> [If people want a different configure option than --enable-maintainer-mode
> than it'll involve a bit more work, but it's still all s.o.p.]
>
> I really don't think I'm asking for anything unusual or excessive.
If what you're asking is trivial to do, then sure, I agree! I mean,
we've gone this far already, right? :-)
Thanks for the e-mail, and sorry if I sounded harsh.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-05-12 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a11c3b928756ec20515e95aba@google.com>
2015-05-12 21:47 ` Fwd: " Doug Evans
2015-05-12 22:02 ` Sergio Durigan Junior
2015-05-12 22:44 ` Doug Evans
2015-05-12 23:26 ` Sergio Durigan Junior [this message]
2015-05-10 19:01 [PATCH v3 00/17] Catch " Sergio Durigan Junior
2015-05-11 0:28 ` [PATCH v4 0/4] catch " Gabriel Krisman Bertazi
2015-05-13 10:47 ` Pedro Alves
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=874mnhjs22.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=dje@google.com \
--cc=gabriel@krisman.be \
--cc=gdb-patches@sourceware.org \
--cc=palves@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