Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot rebuild autobuild
Date: Wed, 29 Nov 2017 22:19:27 +0100	[thread overview]
Message-ID: <20171129211926.GA16373@x230> (raw)
In-Reply-To: <d76cd131-a5ec-631d-4c8b-4bb3d09fd2ca@mind.be>

Hi,

> > So, this is a change in behaviour, and should be reported upstream as a
> > bug. Will you do so?

>  As I explained in the extended commit message when I applied the patch fixing
> this (b9d2d4cb4eb: "Fix makefile include order by using sort/wildcard.") make
> actually has had this behaviour "forever" (since make 3.82). It calls glob with
> GLOB_NOSORT. Note that in most of the cases where we didn't already do $(sort
> $(wildcard ...)), the order actually doesn't (or shouldn't) matter. For example,
> package/*/*.mk hopefully does not depend on the order. In other words, it's very
> likely that nobody notices if things get included in the "wrong" order.
Even though I understand that the change in 3.82 you pointed out *should* change the
behavior, it's different: 3.82 is working.

>  As far as I could see, only the external-toolchain-package really could cause
> any problems.

>  So my guess is that the bisected commit really has nothing to do with it, it
> just happens to trigger the random ordering issue.
I don't understand changes in 4fd5672 ("Use Jenkins hash.") [2], but it does it
permanently (I tested it several times). That's why I thought it would be good to notify
upstream. Now I'm not sure (I haven't reported it yet).

>  Now that I look at it again, however, it looks like we haven't been able to
> adequately explain why this issue suddenly occurred... First of all,
> external-toolchain-package has existed for a year now, so if it is truly random
> we'd expect someone to have noticed before. Also, the change in Tumbleweed that
> Petr pointed to [1] should actually *fix* the issue, because it removes the
> NOSORT. Debian and Ubuntu, conversely, have no such patch so the autobuilders
> should see this issue (they use external toolchains a lot)...
I've been testing buildroot in Debian unstable for few years and in openSUSE Tumbleweed
for about one year. I never noticed this, until now. You can see from [3], that the only
thing that changed in openSUSE's make is glob-lstat.patch [4]. It actually changes glob,
so it can be relevant. I can test it with and without it this week.
In Debian I've been testing it probably on 3.81, 4.0 and 4.1.

>  /me is confused again...


>  Regards,
>  Arnout


Kind regards,
Petr


[1] https://build.opensuse.org/package/view_file/Base:System/make/make-sorted-glob.patch?expand=1
[2] https://git.savannah.gnu.org/cgit/make.git/commit/?id=4fd56724ad281498d3c8b27a4b25b4070f6e4e65
[3] https://build.opensuse.org/package/view_file/Base:System/make/make.changes?expand=1
[4] https://build.opensuse.org/package/view_file/Base:System/make/glob-lstat.patch?expand=1

  reply	other threads:[~2017-11-29 21:19 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
2017-11-25 16:34                       ` Arnout Vandecappelle
2017-11-29 21:19                         ` Petr Vorel [this message]
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=20171129211926.GA16373@x230 \
    --to=petr.vorel@gmail.com \
    --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