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: Sun, 16 Jul 2017 17:08:59 +0200 [thread overview]
Message-ID: <20170716150859.GD30047@scaer> (raw)
In-Reply-To: <CAGt4E5txWySKpD0npytd=8yujrcQRQNQXwgYQzGCLdy9hyLTLw@mail.gmail.com>
Peter, Thomas, Arnout, All,
Your position on Markus' (non-)issue?
Do we keep the code as-is, or do we "fix" it so that it is not
ambiguous?
I've checked, and make uses strcmp(3) internally, and strcmp() does not
use locales at all; it just compares chars.
Regards,
Yann E. MORIN.
On 2017-07-13 16:59 -0700, Markus Mayer spake thusly:
> On 13 July 2017 at 14:45, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > Markus, All,
> >
> > On 2017-07-13 13:16 -0700, Markus Mayer spake thusly:
> > [--SNIP--]
> >> I think I may need some help. I started implementing the suggested
> >> solution, but I have run into some unexpected problems.
> >>
> >> Specifically, if I move the linux-tool-*.mk files into their own
> >> sub-directory, all linux-tools related targets disappear. It won't
> >> build any linux-tools during a regular run of 'make' and it will
> >> actually say "No rule..." when explicitly asked to build linux-tools:
> >>
> >> $ make linux-tools
> >> umask 0022 && make -C /home/mmayer/Development/buildroot
> >> O=/home/mmayer/Development/output/arm64/. linux-tools
> >> make[1]: *** No rule to make target 'linux-tools'. Stop.
> >> Makefile:16: recipe for target '_all' failed
> >> make: *** [_all] Error 2
> >>
> >> Here's what I have done:
> >>
> >> (mmayer at lbrmn-mmayer) ~/Development/buildroot$ l package/linux-tools/
> >> total 84
> >> drwxrwxr-x 3 mmayer mmayer 4096 Jul 13 11:38 .
> >> drwxrwxr-x 1843 mmayer mmayer 65536 Jul 10 12:28 ..
> >> -rw-rw-r-- 1 mmayer mmayer 2577 Jul 10 11:02 Config.in
> >> -rw-rw-r-- 1 mmayer mmayer 2049 Jul 13 11:20 linux-tools.mk
> >> drwxrwxr-x 2 mmayer mmayer 4096 Jul 13 11:20 tools
> >
> > OK, I will attempt a wild gues here... Rename the 'tools' directory to
> > 'linux-tools' and try again.
>
> Your guess was spot-on. That was exactly it.
>
> [...]
>
> > We have a similar situation in linux/linux.mk, see line 425 where we
> > have an explanation about this:
> >
> > 423 # Include all our extensions.
> > 424 #
> > 425 # Note: our package infrastructure uses the full-path of the last-scanned
> > 426 # Makefile to determine what package we're currently defining, using the
> > 427 # last directory component in the path. As such, including other Makefile,
> > 428 # like below, before we call one of the *-package macro is usally not
> > 429 # working.
> > 430 # However, since the files we include here are in the same directory as
> > 431 # the current Makefile, we are OK. But this is a hard requirement: files
> > 432 # included here *must* be in the same directory!
> > 433 include $(sort $(wildcard linux/linux-ext-*.mk))
> >
> > So I would argue against the sub-directory, but in favour of renaming
> > the files.
> >
> > Except that is not necessary, is it? IIRC, you confirmed that this was
> > in fact not a problem, right?
>
> Yes, it is not a problem for linux-tool-tmon.mk. I originally thought it was.
>
> > So, rather than try to fix a problem that does not exist, using fragile
> > heuristics, I would recommend we keep the status-quo.
>
> It was my understanding that the alphabetical sorting of linux-tools
> has been considered to be not really all that desirable and that a
> "once and for all" solution that does away with this requirement would
> be welcomed. That's why I looked into these changes.
>
> I'll leave the decision to the maintainers as to whether this should
> be changed (either using a sub-directory or an file extension other
> than .mk) or if it is preferable to keep the alphabetical sorting. My
> personal take is that relying on alphabetical sorting is more fragile
> than the alternate solution, but it is up to you guys.
>
> Thanks,
> -Markus
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-07-16 15:08 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
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 [this message]
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=20170716150859.GD30047@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