From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot rebuild autobuild
Date: Sat, 25 Nov 2017 16:01:44 +0100 [thread overview]
Message-ID: <20171125150144.GC2798@scaer> (raw)
In-Reply-To: <20171121201605.tzmasudql66iruxa@dell5510>
Petr, All,
On 2017-11-21 21:16 +0100, Petr Vorel spake thusly:
> > > If the *.mk is expanded in alphabetical order, pkg-toolchain-external.mk will
> > > always come before toolchain-external.mk. Otherwise it is possible (depending on
> > > the state of hash tables or inode numbers or whatever) that
> > > toolchain-external-custom.mk gets included first.
[--SNIP--]
> I found by bisecting that our bug is caused by this change in make:
> 4fd5672 ("Use Jenkins hash.")
> https://git.savannah.gnu.org/cgit/make.git/commit/?id=4fd56724ad281498d3c8b27a4b25b4070f6e4e65
Good work at bisecting it! :-)
> It's a version after last release (4.2.1).
> I wonder whether it's a bug in make (I guess so) and whether we should report it
> (probably).
This is indeed a change in behaviour. However, as make ever documented
a guranteed/non-guaranteed ordering of wildcards to begin with?
The manual for the current make version says nothing about the ordering,
and neither do the manual for older versions (I've checked only a few of
them).
So, this is a change in behaviour, and should be reported upstream as a
bug. Will you do so?
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-11-25 15:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 10:27 [Buildroot] Cannot rebuild autobuild Petr Vorel
2017-11-13 11:06 ` Baruch Siach
2017-11-13 14:42 ` Petr Vorel
2017-11-14 22:44 ` Peter Seiderer
2017-11-15 12:58 ` Petr Vorel
2017-11-15 23:03 ` Arnout Vandecappelle
2017-11-15 23:19 ` Peter Seiderer
2017-11-15 23:40 ` Arnout Vandecappelle
2017-11-16 7:29 ` Petr Vorel
2017-11-16 13:43 ` Arnout Vandecappelle
2017-11-18 21:22 ` Peter Seiderer
2017-11-20 21:44 ` Yann E. MORIN
2017-11-18 21:32 ` Peter Seiderer
2017-11-21 20:16 ` Petr Vorel
2017-11-25 15:01 ` Yann E. MORIN [this message]
2017-11-25 16:34 ` Arnout Vandecappelle
2017-11-29 21:19 ` Petr Vorel
2017-12-15 20:22 ` Petr Vorel
2017-12-15 20:23 ` [Buildroot] FW: " Kees van Unen
2017-11-16 7:14 ` [Buildroot] " Petr Vorel
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=20171125150144.GC2798@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