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 1/2] Makefile: don't rely on linux-tools being sorted alphabetically
Date: Wed, 5 Jul 2017 09:38:07 +0200	[thread overview]
Message-ID: <20170705073807.GF3499@scaer> (raw)
In-Reply-To: <20170705072538.GE3499@scaer>

Markus, All,

On 2017-07-05 09:25 +0200, Yann E. MORIN spake thusly:
> On 2017-07-04 16:54 -0700, Markus Mayer spake thusly:
> > From: Markus Mayer <mmayer@broadcom.com>
> > 
> > The Linux tools master makefile (linux-tools.mk) must be included after
> > all Linux tools sub-makefiles (linux-tool-*.mk). This is currently
> > ensured by sorting all package makefiles alphabetically.
> > 
> > In preparation for adding linux-tool-tmon, we cannot keep relying on
> > this mechanism. In the C locale, linux-tool-tmon.mk will be sorted
> > behind linux-tools.mk, which would break the build.
[--SNIP--]
> However, I am totally in favour of fixing it once and for all.
> 
> But rather than do a hack in the main Makefile as you suggest, I would
> just ensure the ordering of the files.
> 
> I think we should just rneame the individual tool files to remove
> the .mk extension, and then exp[licitly source them from
> package/linux-tools/linux-tools.mk
> 
>     include $(wildcard package/linux-tools/linux-tool-*)
> 
> and be done with that once and for all.

But don't hurry in doing so, we've been discussing this IRL with Thomas,
and he is not happy with that proposal (but he agrees that touching the
main Makefile is not acceptable).

We're looking to find an alternative solution...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  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-05  7:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04 23:54 [Buildroot] [PATCH 0/2] Add linux-tool-tmon Markus Mayer
2017-07-04 23:54 ` [Buildroot] [PATCH 1/2] Makefile: don't rely on linux-tools being sorted alphabetically Markus Mayer
2017-07-05  7:25   ` Yann E. MORIN
2017-07-05  7:38     ` Yann E. MORIN [this message]
2017-07-05  8:15       ` Arnout Vandecappelle
2017-07-05  8:09     ` Arnout Vandecappelle
2017-07-05  8:18       ` Arnout Vandecappelle
     [not found]         ` <CAGt4E5ueb6x_S4ff=dAeK-x9JnO1SmhnUGz+Q3XKUtj6s24L_Q@mail.gmail.com>
2017-07-05 17:19           ` Markus Mayer
2017-07-08 21:16             ` Arnout Vandecappelle
2017-07-09  0:00               ` Markus Mayer
2017-07-09  8:13             ` Yann E. MORIN
2017-07-09 11:10               ` Arnout Vandecappelle
2017-07-09 12:41                 ` Yann E. MORIN
2017-07-10  3:49                   ` Markus Mayer
2017-07-13 20:16                     ` Markus Mayer
2017-07-13 21:45                       ` Yann E. MORIN
2017-07-13 23:59                         ` Markus Mayer
2017-07-16 15:08                           ` Yann E. MORIN
2017-07-17  7:37                             ` Thomas Petazzoni
2017-07-17 15:36                               ` Yann E. MORIN
2017-07-17 17:32                                 ` Markus Mayer
2017-07-04 23:54 ` [Buildroot] [PATCH 2/2] package/linux-tools: add tmon Markus Mayer

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=20170705073807.GF3499@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