Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-tools: change method for including linux-tool sub-makefiles
Date: Tue, 18 Jul 2017 21:38:38 +0200	[thread overview]
Message-ID: <20170718193838.GB2583@scaer> (raw)
In-Reply-To: <CAGt4E5vAHZWoU4rzmv0-AwNm4rCuG9QYVcn+V0A80UevEuSNLw@mail.gmail.com>

Markus, All,

On 2017-07-18 12:36 -0700, Markus Mayer spake thusly:
> On 18 July 2017 at 12:06, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Markus, All,
> >
> > On 2017-07-18 11:11 -0700, Markus Mayer spake thusly:
> >> Make inclusion ordering of all linux-tool-*.mk sub-makefiles explicit
> >> instead of relying on alphabetical sort order. This is done by
> >> renaming the Linux tools sub-makefiles to the format linux-tool-*.mk.in.
> >> This causes the top-level Makefile to ignore the Linux tools
> >> sub-makefiles.
> >>
> >> Until now, the main Makefile included all linux-tool-*.mk files, as
> >> well as linux-tools.mk, and it relied on alphabetical sorting to
> >> include them in the proper order (linux-tool-*.mk before
> >> linux-tools.mk).
> >>
> >> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> >
> > Thank you for this new iteration.
> >
> > I have a small comment, see below...
> >
> > [--SNIP--]
> >> diff --git a/package/linux-tools/linux-tools.mk b/package/linux-tools/linux-tools.mk
> >> index 7fa8d19..2827ade 100644
> >> --- a/package/linux-tools/linux-tools.mk
> >> +++ b/package/linux-tools/linux-tools.mk
> >> @@ -10,15 +10,13 @@
> >>  #
> >>  # So, all tools refer to $(LINUX_DIR) instead of $(@D).
> >>
> >> -# Note: we need individual tools .mk files to be included *before* this one
> >> -# to guarantee that each tool has a chance to register itself before we build
> >> -# the list of build and install hooks, below.
> >> -#
> >> -# This is currently guaranteed by the naming of each file:
> >> -# - they get included by the top-level Makefile, with $(sort $(wildcard ...))
> >> -# - make's $(sort) function will aways sort in the C locale
> >> -# - the files names correctly sort out in the C locale so that each tool's
> >> -#   .mk file is included before this one.
> >> +# Note: we need individual tools makefiles to be included *before* we build
> >> +# the list of build and install hooks below to guarantee that each tool has
> >> +# a chance to register itself. Therefore, the makefiles are named
> >> +# linux-tool-*.mk.in, so they won't be picked up by the top-level Makefile,
> >> +# but can be included here, guaranteeing proper ordering.
> >
> > There are two important and crucial points:
> >
> >   - guaranteeing inclusion ordering,
> >   - guaranteeing single inclusion.
> >
> > If only the first were needed, then we could simply include the tools
> > here without renaming; they'd be included twice, but that is not a
> > problem for the first point.
> >
> > But the second point is also important, because we do not want tools to
> > register themselves twice, nor do we want they break their variables by
> > appending stuff already added.
> >
> > So, I would keep your comment as is, except I'd add a bit on the third
> > and last lines:
> >
> > # Note: we need individual tools makefiles to be included *before* we build
> > # the list of build and install hooks below to guarantee that each tool has
> > # a chance to register itself once, and only once. Therefore, the makefiles
> > # are named linux-tool-*.mk.in, so they won't be picked up by the top-level
> > # Makefile, but can be included here, guaranteeing the single inclusion and
> > # the proper ordering.
> 
> That makes perfect sense to me. Thanks for adding it.
> 
> > (Bonus point: ithe comment all lines up perfectly well, now! ;-] )
> >
> > No need to respin, I gues, a maintainer can tweak the message when
> > applying.
> 
> Sure. I'll hold off for now. Should this change for whatever reason,
> please let me know, and I'll send an updated revision.

Since we agree, and with the above ammended at commit time:

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> > Thanks! :-)
> >
> > Regards,
> > Yann E. MORIN.
> >
> >> +include $(sort $(wildcard package/linux-tools/*.mk.in))
> >>
> >>  # We only need the kernel to be extracted, not actually built
> >>  LINUX_TOOLS_PATCH_DEPENDENCIES = linux
> >> --
> >> 2.7.4
> >>
> >> _______________________________________________
> >> buildroot mailing list
> >> buildroot at busybox.net
> >> http://lists.busybox.net/mailman/listinfo/buildroot
> >
> > --
> > .-----------------.--------------------.------------------.--------------------.
> > |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> > | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> > | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> > | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> > '------------------------------^-------^------------------^--------------------'

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-07-18 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 18:11 [Buildroot] [PATCH] package/linux-tools: change method for including linux-tool sub-makefiles Markus Mayer
2017-07-18 19:06 ` Yann E. MORIN
2017-07-18 19:36   ` Markus Mayer
2017-07-18 19:38     ` Yann E. MORIN [this message]
2017-07-19 19:35 ` Thomas Petazzoni

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=20170718193838.GB2583@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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