Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Gabriel Krisman Bertazi <gabriel@krisman.be>, gdb-patches@sourceware.org
Cc: sergiodj@redhat.com, dje@google.com
Subject: Re: [RESEND PATCH v6 4/5] Include group information to xml syscall files.
Date: Fri, 27 May 2016 10:18:00 -0000	[thread overview]
Message-ID: <7adaf517-55f7-8773-749c-767fe0a37406@redhat.com> (raw)
In-Reply-To: <1463713807-11250-1-git-send-email-gabriel@krisman.be>

On 05/20/2016 04:10 AM, Gabriel Krisman Bertazi wrote:
> Patch 4/5 bounced due to size. Resending with -M to detect renames...

Thanks, that's the right thing to do, even without bounces.  Best is
to adjust the git config to make that the default.

On 05/20/2016 04:10 AM, Gabriel Krisman Bertazi wrote:
> --- /dev/null
> +++ b/gdb/syscalls/apply-defaults.xsl
> @@ -0,0 +1,31 @@
> +<!-- Copyright (C) 2016 Free Software Foundation, Inc.
> +
> +     Copying and distribution of this file, with or without modification,
> +     are permitted in any medium without royalty provided the copyright
> +     notice and this notice are preserved.  -->
> +

Shouldn't this file be GPLv3+ like all other build or source files?

> We maintain linux-defaults.xml.in, a template file to hold generic group
> information.  It is used by the XSL script that parses the architecture
> specific files to generate the final xml files, which are actually
> installed and loaded by GDB.  The script is not run during the normal
> build process, only when building in maintainer mode.

> +@MAINTAINER_MODE_TRUE@%.xml: %.xml.in apply-defaults.xsl linux-defaults.xml.in
> +@MAINTAINER_MODE_TRUE@	$(XSLTPROC) -o $(SYSCALLS_SRCDIR)/$@ $(SYSCALLS_SRCDIR)/apply-defaults.xsl $<;\
> +

Please always define the rules in the Makefile.in even without
maintainer mode.  What you want is force the _dependencies_ when maintainer
mode is active, but leave them out otherwise.
That would make it possible to force-regenerate the files even when
not using maintainer mode.

See e.g.,: gdb/Makefile.in:

$(srcdir)/aclocal.m4: @MAINTAINER_MODE_TRUE@ $(aclocal_m4_deps)
...

So that'd be something like:

%.xml: @MAINTAINER_MODE_TRUE@ %.xml.in apply-defaults.xsl linux-defaults.xml.in
	$(XSLTPROC) -o $(SYSCALLS_SRCDIR)/$@ $(SYSCALLS_SRCDIR)/apply-defaults.xsl $<;\

It'd be convenient to add a rule to regenerate all xml files, something like:

.PHONY syscall-xml
syscall-xml: $(SYSCALLS_FILES)

.PHONY clean-syscall-xml
clean-syscall-xml: $(SYSCALLS_FILES)
	rm -f $(SYSCALLS_FILES)

Thanks,
Pedro Alves


  parent reply	other threads:[~2016-05-27 10:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 17:28 [PATCH v5 " Doug Evans
2016-05-20  2:30 ` Gabriel Krisman Bertazi
2016-05-20  2:56   ` [PATCH v6 1/5] Implemement support for groups of syscalls in the xml-syscall interface Gabriel Krisman Bertazi
2016-05-20  2:56     ` [PATCH v6 3/5] Add tests for catching groups of syscalls on supported architectures Gabriel Krisman Bertazi
2016-05-26 18:18       ` Sergio Durigan Junior
2016-05-20  2:56     ` [PATCH v6 2/5] Add support to catch groups of syscalls Gabriel Krisman Bertazi
2016-05-26 18:17       ` Sergio Durigan Junior
2016-05-20  2:56     ` [PATCH v6 5/5] Update documentation on catching a group of related syscalls Gabriel Krisman Bertazi
2016-05-20  5:48       ` Eli Zaretskii
2016-05-26 18:22     ` [PATCH v6 1/5] Implemement support for groups of syscalls in the xml-syscall interface Sergio Durigan Junior
2016-05-20  3:10   ` [RESEND PATCH v6 4/5] Include group information to xml syscall files Gabriel Krisman Bertazi
2016-05-26 18:14     ` Sergio Durigan Junior
2016-05-27 10:18     ` Pedro Alves [this message]
2016-06-19 20:37       ` Gabriel Krisman Bertazi

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=7adaf517-55f7-8773-749c-767fe0a37406@redhat.com \
    --to=palves@redhat.com \
    --cc=dje@google.com \
    --cc=gabriel@krisman.be \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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