All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot rebuild autobuild
Date: Thu, 16 Nov 2017 14:43:48 +0100	[thread overview]
Message-ID: <d13312cf-ae70-92fd-8819-a86c79d1723b@mind.be> (raw)
In-Reply-To: <20171116072948.smctbcvxwkxgqoah@x230>



On 16-11-17 08:29, Petr Vorel wrote:
> Hi,
> 
> ...
>>> make[1]: *** No rule to make target 'toolchain-external-custom', needed by '.../build-prebuild-toolchain-001/build/toolchain-external/.stamp_configured'.  Stop.
>>> make: *** [Makefile:16: _all] Error 2
> 
>>> The error occurs  before the prebuild toolchain is downloaded/extracted...
> 
>>  That is really weird, the toolchain-external-custom dependencies should be
>> defined no matter what... Could you pastebin the output make 'make -qp' somewhere?
> Here it is:
> http://sipe.cz/buildroot/out.log (68M)
> http://sipe.cz/buildroot/out.log.tar.gz (9MB)

 Oh boy...

 The problem is that on Tumbleweed the order of inclusion seems to be different,
which causes toolchain-external-package not to be defined at the time that
toolchain-external-custom.mk is included (same for all other external toolchains).

Makefile:492:include toolchain/*/*.mk

This causes inclusion of
toolchain/toolchain-external/toolchain-external.mk:28:include
toolchain/toolchain-external/*/*.mk
and
toolchain/toolchain-external/pkg-toolchain-external.mk:592:toolchain-external-package
= ...

 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.

 The short-term solution is of course $(sort $(wildcard ...))

 But for the long term, I think it's better to move pkg-*.mk to support/misc (or
maybe to support/make) and organise the order of inclusion from there.

 Any takers? Yann?

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2017-11-16 13:43 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 [this message]
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
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=d13312cf-ae70-92fd-8819-a86c79d1723b@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.